* Help with rebase after cvsimport
[not found] <bcd06dea1003250935q324b2412g959309070491c73c@mail.gmail.com>
@ 2010-03-25 17:37 ` Brice Ruth
2010-03-26 9:17 ` Michael J Gruber
0 siblings, 1 reply; 3+ messages in thread
From: Brice Ruth @ 2010-03-25 17:37 UTC (permalink / raw)
To: git
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?
Any help would be appreciated!
Thanks,
Brice Ruth, FCD
Software Engineer, Madison WI
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Help with rebase after cvsimport
2010-03-25 17:37 ` Help with rebase after cvsimport Brice Ruth
@ 2010-03-26 9:17 ` Michael J Gruber
[not found] ` <bcd06dea1003260910h6e27fdfbh9f968bf5ca4c1b6e@mail.gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Michael J Gruber @ 2010-03-26 9:17 UTC (permalink / raw)
To: Brice Ruth; +Cc: git
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Help with rebase after cvsimport
[not found] ` <bcd06dea1003260910h6e27fdfbh9f968bf5ca4c1b6e@mail.gmail.com>
@ 2010-03-27 17:22 ` Michael J Gruber
0 siblings, 0 replies; 3+ messages in thread
From: Michael J Gruber @ 2010-03-27 17:22 UTC (permalink / raw)
To: Brice Ruth, Git Mailing List
Brice Ruth venit, vidit, dixit 26.03.2010 17:10:
> So, when you write "Note that by doing that you basically discard your
> version of commits which made the git-cvs-git roundtrip" - I will lose
> the individual commits I made locally and I'll just see the *one*
> exportcommit that I made for my local changes, is that right?
The way I use git-cvs, I have one cvs commit per git commit. Are you
using it differently?
The rebase will discard those commits whose patch text is already
"present" on the branch. I assume that for a cumulative patch this means
it's not ignored - in that case the rebase won't buy you anything.
Michael
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-03-27 17:22 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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
[not found] ` <bcd06dea1003260910h6e27fdfbh9f968bf5ca4c1b6e@mail.gmail.com>
2010-03-27 17:22 ` Michael J Gruber
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).