depot_tools should be case-insensitive when reasoning on git branches |
||
Issue descriptionSee internal G+ thread for more context: https://plus.google.com/115755526207180381638/posts/ZbdYbSPoE9W depot_tools seems to track metadata separately depending on the branch casing. E.g: $ git checkout foo $ git cl upload $ git checkout Foo $ git cl upload cat .git/config [branch "Foo"] base = 3047eb429a218092bd9cf5d46dffa5a78834d216 base-upstream = refs/remotes/origin/master [branch "foo"] base = 3047eb429a218092bd9cf5d46dffa5a78834d216 base-upstream = refs/remotes/origin/master which seems wrong to me, as "foo" and "Foo" are the same branch really.
,
Jul 26 2017
Oh excellent point, I think what was missing in my bug is "When on case-insensitive filesystems:". Although in general I feel would be fine if depot_tools was more aggressive and shout if you end up having "foo" and "Foo" being distinct branches on a case-sensitive file-system.
,
Jul 26
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by pkasting@chromium.org
, Jul 26 2017