From: Michael Haggerty <mhagger@alum.mit.edu>
To: Marko Macek <marko.macek@gmx.net>
Cc: Jon Smirl <jonsmirl@gmail.com>, git@vger.kernel.org
Subject: Re: Some tips for doing a CVS importer
Date: Mon, 27 Nov 2006 12:29:06 +0100 [thread overview]
Message-ID: <456ACC02.6090508@alum.mit.edu> (raw)
In-Reply-To: <4569BCB8.9030809@gmx.net>
Marko Macek wrote:
>> Another note for doing a converter. When combining things into change
>> sets, for git import the comments in the branches should not be mixed
>> between branches and the trunk when detecting change set. Git doesn't
>> allow simultaneous commits to the trunk and branches.
>
> Yup, this is the current problem I'm facing now. Even for CVS->SVN
> conversion,
> I don't want to see multi-branch commits.
To avoid multi-branch commits, you have to start cvs2svn with an
--options file, and in the options file set
ctx.cross_project_commits = False
next prev parent reply other threads:[~2006-11-27 11:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 21:49 Some tips for doing a CVS importer Jon Smirl
2006-11-20 23:03 ` Martin Langhoff
2006-11-20 23:37 ` Jon Smirl
2006-11-21 0:29 ` Martin Langhoff
2006-11-21 0:55 ` Carl Worth
2006-11-21 1:40 ` Jon Smirl
2006-11-21 6:39 ` Shawn Pearce
2006-11-21 19:56 ` lamikr
2006-11-21 20:05 ` Shawn Pearce
2006-11-23 19:45 ` Robin Rosenberg
2006-11-25 6:59 ` Shawn Pearce
2006-11-21 20:03 ` Petr Baudis
2006-11-21 20:15 ` Shawn Pearce
2006-11-21 20:22 ` Johannes Schindelin
2006-11-23 9:10 ` Johannes Sixt
2006-11-21 20:40 ` Martin Langhoff
2006-11-21 1:53 ` Jon Smirl
2006-11-26 10:18 ` Marko Macek
2006-11-26 15:35 ` Jon Smirl
2006-11-26 16:11 ` Marko Macek
2006-11-26 17:51 ` Jon Smirl
2006-11-27 11:29 ` Michael Haggerty [this message]
2006-11-21 6:43 ` Shawn Pearce
2006-11-27 11:24 ` Michael Haggerty
2006-11-27 11:51 ` Markus Schiltknecht
2006-11-27 22:09 ` Michael Haggerty
2006-11-28 15:18 ` Markus Schiltknecht
2006-11-30 0:35 ` Michael Haggerty
2006-11-30 0:45 ` Daniel Jacobowitz
2006-11-27 15:20 ` Jon Smirl
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=456ACC02.6090508@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=marko.macek@gmx.net \
/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).