From: Michael J Gruber <git@drmicha.warpmail.net>
To: Brice Ruth <bdruth@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Help with rebase after cvsimport
Date: Fri, 26 Mar 2010 10:17:32 +0100 [thread overview]
Message-ID: <4BAC7BAC.7030507@drmicha.warpmail.net> (raw)
In-Reply-To: <bcd06dea1003251037j492bfbbcx2f99ad5046169f2@mail.gmail.com>
Brice Ruth venit, vidit, dixit 25.03.2010 18:37:
> Posted this to #git but it seemed like everyone was asleep (or clueless)
>
> [11:22] <Brice> Good morning - I have a quick question on using git
> rebase with git cvsimport - I'm trying to eliminate the duplicate 'cvs
> import' commit created when the cvs import is merged in - I'm just not
> sure what 'rebase' I need to do after a git cvsimport. Help?
> [11:22] <Brice> I'm on master when I do cvsimport
> [11:23] <Brice> cvsimport is run with -r cvs
> [11:23] <Brice> so, am I in the right ballpark thinking I need to git
> rebase cvs?
You have basically 2 options, see, e.g., the last paragraphs of
http://grubix.blogspot.com/2009/11/git-over-cvs.html
It seems you want to go with 1. In that case you need to
git rebase cvs/master master
(you can leave out the second argument if you are on master). Note that
by doing that you basically discard your version of commits which made
the git-cvs-git roundtrip (committed in git, cvsexported to cvs,
cvsimported to git). That's why I use approach 2 mentioned there, but it
depends certainly on your usage scenario, whether cvs is the
central/authoritative repo on which you work with git, or the other way
round.
Cheers,
Michael
next prev parent reply other threads:[~2010-03-26 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bcd06dea1003250935q324b2412g959309070491c73c@mail.gmail.com>
2010-03-25 17:37 ` Help with rebase after cvsimport Brice Ruth
2010-03-26 9:17 ` Michael J Gruber [this message]
[not found] ` <bcd06dea1003260910h6e27fdfbh9f968bf5ca4c1b6e@mail.gmail.com>
2010-03-27 17:22 ` Michael J Gruber
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=4BAC7BAC.7030507@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=bdruth@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).