git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Khomoutov <kostix+git@007spb.ru>
To: "Samuel Åslund" <samuel@update.uu.se>
Subject: Re: Git documentation on branching.
Date: Mon, 10 Apr 2017 10:13:36 +0300	[thread overview]
Message-ID: <20170410101336.c93a423e7d3a8594151bebef@domain007.com> (raw)
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:

> 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?

  reply	other threads:[~2017-04-10  7:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10  6:56 Git documentation on branching Samuel Åslund
2017-04-10  7:13 ` Konstantin Khomoutov [this message]
     [not found]   ` <a967439f-117e-1f09-6f40-7f62bc6cbae1@update.uu.se>
2017-04-10 17:13     ` Konstantin Khomoutov
2017-04-10 10:21 ` Ævar Arnfjörð Bjarmason
2017-04-10 10:45   ` Samuel Åslund
2017-04-10 10:59     ` Ævar Arnfjörð Bjarmason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170410101336.c93a423e7d3a8594151bebef@domain007.com \
    --to=kostix+git@007spb.ru \
    --cc=samuel@update.uu.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).