git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: GIT <git@vger.kernel.org>
Subject: Re: Switching heads and head vs branch after CVS import
Date: Mon, 15 Aug 2005 14:05:14 +1200	[thread overview]
Message-ID: <46a038f905081419057cc6b5cd@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0508141737270.3553@g5.osdl.org>

> Just do
> 
>         git checkout branch-name
> 
> to switch between them.

thanks! I was doing cg-branch-chg branch-name and it wasn't working.

> So in a cvsimport, you'll never see a merge back to the head, even if one
> technically took place.

There may be some surprises in here! gitk --all shows at least one
branch opening and merging back into origin, and it has figured it out
correctly: that was a feature branch where people worked on for a
while and merged back. I haven't had time to explore it more, but it
looks promising.

Except for the keyword expansion. surely there's a way to tell cvsps
to not do it. Why would we ever want it?

> > And I am confused about the difference between heads and branches.
> 
> Confusion of naming.
> 
> branches and heads are the same thing in git. 

right. There are two separate directories in .git for them, so I was
misled by that. Should I assume git is safe from name clashes or is it
up to porcelain to deal with such minutiae?

> They are "proper branches", and sorry about the confusion. 

Don't worry! Means I'll have to wake up and pay attention from now on...

thanks,


martin

  reply	other threads:[~2005-08-15  2:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15  0:24 Switching heads and head vs branch after CVS import Martin Langhoff
2005-08-15  0:40 ` Junio C Hamano
2005-08-15  0:46 ` Linus Torvalds
2005-08-15  2:05   ` Martin Langhoff [this message]
2005-08-15  2:49     ` Linus Torvalds
2005-08-15  8:22       ` Sven Verdoolaege
2005-08-15  9:07       ` Matthias Urlichs
2005-08-15  9:48         ` Martin Langhoff
2005-08-15  8:09   ` Wolfgang Denk
2005-08-15 10:38     ` Matthias Urlichs
2005-08-15 11:45       ` Sven Verdoolaege
2005-08-15 16:42     ` Linus Torvalds
2005-08-15 20:09       ` Martin Langhoff
2005-08-15 20:22         ` Wolfgang Denk
2005-08-15 22:37         ` Linus Torvalds
2005-08-15 22:53           ` Johannes Schindelin

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=46a038f905081419057cc6b5cd@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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).