From: "David Symonds" <dsymonds@gmail.com>
To: "Dima Kagan" <dima.kagan@gmail.com>
Cc: "Jakub Narebski" <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: Git branches - confusing behavior
Date: Sun, 11 May 2008 22:06:19 +1000 [thread overview]
Message-ID: <ee77f5c20805110506i58dc735fqb6f4258dbb67bf27@mail.gmail.com> (raw)
In-Reply-To: <4826DF6A.2070306@gmail.com>
On Sun, May 11, 2008 at 9:58 PM, Dima Kagan <dima.kagan@gmail.com> wrote:
> That's a subjective point of view :) I'm coming from the SVN world and uncommitted changes on one branch don't affect other branches. Is there a way I can achieve this behavior with git?
If you *really* want SVN's behaviour of "branches", just copy your
whole working tree (including the .git directory) and start making
changes in that. Then they'll be completely separate and you can just
'cd' between them.
Dave.
next prev parent reply other threads:[~2008-05-11 12:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 11:31 Git branches - confusing behavior Dima Kagan
2008-05-11 11:42 ` Jakub Narebski
2008-05-11 11:58 ` Dima Kagan
2008-05-11 12:06 ` David Symonds [this message]
2008-05-11 12:11 ` Dima Kagan
2008-05-11 12:13 ` David Symonds
2008-05-11 12:17 ` Dima Kagan
2008-05-11 12:20 ` Steve Frécinaux
[not found] ` <f35478f50805110513h15aa462bs9ee35ed4738d3009@mail.gmail.com>
2008-05-11 12:21 ` Dima Kagan
2008-05-11 13:40 ` Jakub Narebski
2008-05-11 12:33 ` Dima Kagan
2008-05-11 12:57 ` Björn Steinbrink
2008-05-11 13:04 ` Dima Kagan
2008-05-11 13:27 ` Björn Steinbrink
2008-05-11 13:39 ` Dima Kagan
[not found] ` <4826F72D.2070205-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-05-11 15:25 ` Patrick Aljord
2008-05-11 15:39 ` Teemu Likonen
2008-05-12 7:49 ` Miles Bader
2008-05-11 14:03 ` Theodore Tso
-- strict thread matches above, loose matches on Subject: below --
2008-06-30 7:23 Matt Seitz (matseitz)
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=ee77f5c20805110506i58dc735fqb6f4258dbb67bf27@mail.gmail.com \
--to=dsymonds@gmail.com \
--cc=dima.kagan@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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).