* Possible bug: Changing branch with file locked
@ 2020-07-09 11:01 Antti Tanskanen
0 siblings, 0 replies; only message in thread
From: Antti Tanskanen @ 2020-07-09 11:01 UTC (permalink / raw)
To: git
Hi,
I want to inform you about the fact when I changed a branch with VS
Code open and git did not have permissions to address some files in
the other branch (or in current branch). I got an error message. That
is OK, but my current branch got also polluted with files (from the
other branch?). I needed to run “git stash -u” to get rid of those.
I guess this can be reproduced if one locks a file which is in a
branch and changes the branch. Better functionality would be that git
would only show the error message, not to pollute the branch with
files.
Yours,
Antti Tanskanen
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-07-09 11:01 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-09 11:01 Possible bug: Changing branch with file locked Antti Tanskanen
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.