From: Gordon Heydon <gordon@heydon.com.au>
To: git@vger.kernel.org
Subject: git cvsimport branches not consistent with CVS branches
Date: Sun, 08 Jul 2007 10:45:10 +1000 [thread overview]
Message-ID: <46903396.1010507@heydon.com.au> (raw)
Hi,
After some investigation I found that git cvsimport was not importing
branches 100% correctly with CVS.
Git and CVS do branching very differently in that CVS this is done at
the file level (like everything else) and git does it repository wide.
So if I have a CVS repository with the files a, b and c and I branch b
with a `cvs tab -b BRANCH test` on the branch test I will just have the
file b.
If I do a git cvsimport on the test branch there will actually be the
files a, b and c
What I think needs to happen is that when git cvsimport created the
branch in the git repository it needs to delete all files from the
branch that were not branched.
Thanks in advance.
Gordon.
next reply other threads:[~2007-07-08 0:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 0:45 Gordon Heydon [this message]
2007-07-08 5:45 ` git cvsimport branches not consistent with CVS branches Brian Downing
2007-07-08 10:53 ` Robin Rosenberg
2007-07-08 11:47 ` Johannes Schindelin
2007-07-08 12:22 ` Robin Rosenberg
2007-07-08 21:02 ` Brian Downing
2007-07-08 14:38 ` Steffen Prohaska
2007-07-09 4:31 ` Josh Triplett
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=46903396.1010507@heydon.com.au \
--to=gordon@heydon.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.