git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git documentation on branching.

From
KKKonstantin Khomoutov <kostix+git@007spb.ru>
Date
Apr 10, 2017, 07:13 UTC
Message-ID
<20170410101336.c93a423e7d3a8594151bebef@domain007.com>
In-Reply-To
<3563ee7a-1175-2010-7176-0339cd3e60ee@update.uu.se>

On Mon, 10 Apr 2017 08:56:30 +0200 Samuel Åslund <samuel@update.uu.se> wrote:

Show 7 quoted lines
> I just started playing around with branching in git.
> I have been using it more or less as Subversion until now.
> 
> One feature with "git branch xyz" and "git checkout xyz" that is
> rather obvious if you know them but bit me a little since I did not,
> is that uncommitted work in progress is not affected or saved when
> switching between branches.
[...]

But neither is uncommitted work saved anywhere when you do `svn switch` in Subversion which is analogous to `git checkout`.

While I do know quite many people expect Git to somehow "preserve" their work when switching branches without having them do anything, I wonder what in Subversion workflow makes you think Git should have had the behaviour you expected?

Previous: Samuel ÅslundNext: Ævar Arnfjörð Bjarmason
Message 2 of 6 in “Git documentation on branching.”
  1. Samuel ÅslundApr 10, 2017
  2. Konstantin KhomoutovApr 10, 2017
  3. Ævar Arnfjörð BjarmasonApr 10, 2017
  4. Samuel ÅslundApr 10, 2017
  5. Ævar Arnfjörð BjarmasonApr 10, 2017
  6. Konstantin KhomoutovApr 10, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.