git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: GIT <git@vger.kernel.org>
Subject: Switching heads and head vs branch after CVS import
Date: Mon, 15 Aug 2005 12:24:30 +1200	[thread overview]
Message-ID: <46a038f905081417241f9598cc@mail.gmail.com> (raw)

After having done a cvs import of Moodle using git-cvsimport-script
all the cvs branches show up as heads. How do I switch heads within a
checkout? cogito doesn't seem to be able to, and I'm unsure on how to
do it with git.

And I am confused about the difference between heads and branches. Git
and cogito seem  prepared to merge across the heads (using cg-update
for instance, when pointed to a different head merged it in, rather
than switched to it), that would match a workflow where a group of
people maintain very closely related heads and merge constantly
across.

Branches don't seem to have the same expectation or support in the
toolset. Why? What makes a branch different from a head, apart from
the fact that they would be expected to drift further apart?

In any case, should the cvsimport turn cvs branches into git branches
instead of heads? Is there are way to turn a head into a proper
branch?

cheers,

martin

             reply	other threads:[~2005-08-15  0:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15  0:24 Martin Langhoff [this message]
2005-08-15  0:40 ` Switching heads and head vs branch after CVS import Junio C Hamano
2005-08-15  0:46 ` Linus Torvalds
2005-08-15  2:05   ` Martin Langhoff
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=46a038f905081417241f9598cc@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.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).