From: "Nigel Magnay" <nigel.magnay@gmail.com>
To: git <git@vger.kernel.org>
Subject: git-svn, merging et al.
Date: Fri, 16 May 2008 16:50:07 +0100 [thread overview]
Message-ID: <320075ff0805160850r473582d9qc33f71ba7f56dd51@mail.gmail.com> (raw)
Ok - it's Friday and I've got to interact with svn again..
I'm using git-svn, and I've not followed the guidance. Development has
gone on in git branches and merges - but now I need to commit the
changes back into svn, and dcommit is, understandably, not very happy.
I'm intending to instead do something like a
git format-patch svn-branch..git-branch
git checkout svn-branch
... apply all the patches ...
git commit
git svn dcommit
# back to the git work
git checkout git-branch
# this shouldn't have to do merging - but it will have the parents
to make it clear where the last merge happened from ?
git merge svn-branch
I'm happy that I'm bludgeoning changes in one big blob into SVN, as I
can reasonably say 'if you want the real details, go look at gitweb)
I've tried doing this with
git checkout svn-branch
git merge --squash git-branch
But I don't get the result I'm expecting - what have I missed?
next reply other threads:[~2008-05-16 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 15:50 Nigel Magnay [this message]
2008-05-16 17:40 ` git-svn, merging et al Kevin Ballard
2008-05-19 9:14 ` Nigel Magnay
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=320075ff0805160850r473582d9qc33f71ba7f56dd51@mail.gmail.com \
--to=nigel.magnay@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).