From: Miles Bader <miles@gnu.org>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Matthias Andree <matthias.andree@gmx.de>,
"David H. Lynch J.r" <ml@dlasys.net>,
git@vger.kernel.org
Subject: Re: git svn rebase problem
Date: Tue, 19 May 2009 09:56:08 +0900 [thread overview]
Message-ID: <buobpppq5av.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <32541b130905181000v34d5fd6arcb662bff232cb81c@mail.gmail.com> (Avery Pennarun's message of "Mon, 18 May 2009 13:00:25 -0400")
Avery Pennarun <apenwarr@gmail.com> writes:
>> Branches and git-svn don't mix.
>
> That's not exactly true: merging and git-svn don't mix. But rebasing
> works fine.
I've given up on trying to maintain rigid consistency with svn --
git-svn's constant rebasing is just too painful -- and just cherry-pick
everything between my "svn" branch and master, and use master in
conjunction with better-behaved git-only branches. I often end up with
the same commits in a different order on the two branches, but oh well,
not much to do about that I suppose.
This means I often end up cherry-picking long sequences of commits, and
need to deal with conflicts in these cp-sequences. For this reason, I
often wish cherry-pick supported all the fancy features of rebase
(multiple commits, nice handling of conflicts, -i, etc) -- after all
rebasing is really just a special case of cherry-picking.
[I've tried on a shell-script implementation of such an extended
cherry-pick, but soooo many little corner cases to deal with... maybe
it'd be easier to try and generalize git-rebase...?]
-Miles
--
Conservative, n. A statesman enamored of existing evils, as opposed to a
Liberal, who wants to replace them with new ones.
next prev parent reply other threads:[~2009-05-19 0:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 21:21 git svn rebase problem David H. Lynch J.r
2009-05-15 23:53 ` Avery Pennarun
2009-05-16 3:52 ` John Tapsell
2009-05-18 8:38 ` Matthias Andree
2009-05-18 17:00 ` Avery Pennarun
2009-05-19 0:56 ` Miles Bader [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-18 14:06 David H. Lynch J.r
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=buobpppq5av.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=matthias.andree@gmx.de \
--cc=ml@dlasys.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).