Re: Bug^Feature? fetch protects only current working tree branch
- From
- Andreas Heiduk <andreas.heiduk@mathema.de>
- Date
- Jul 24, 2017, 21:51 UTC
- Message-ID
- <3989d621-e0fd-5075-b42a-abe4fff7ff97@mathema.de>
- In-Reply-To
- <xmqqo9saer9f.fsf@gitster.mtv.corp.google.com>
Am 24.07.2017 um 00:13 schrieb Junio C Hamano:
Show 11 quoted lines
> Andreas Heiduk <andreas.heiduk@mathema.de> writes: > >> A `git fetch . origin/master:master` protects the currently checked out >> branch (HEAD) unless the `-u/--update-head-ok` is supplied. This avoids a >> mismatch between the index and HEAD. BUT branches which are HEADs in other >> working trees do not get that care - their state is silently screwed up. >> >> Is this intended behaviour or and just an oversight while implementing >> `git worktree`? > > The latter.
Ok, so I can adjust some of my helper scripts to catch and forbid this case.
Show 6 quoted lines
> [...]"git worktree" is an interesting feature and has > potential to become useful in wider variety of workflows than it > currently is, but end users should consider it still experimental as > it still is with many such small rough edges like this one. > > Patches to help improving the feature is of course very welcome.
Since the core of the check is in C, I'll pass on this one. I could supply a patch adding this to the "BUGS" section of git-worktree(1) though :-)