From: Stephen Haberman <stephen@exigencecorp.com>
To: git@vger.kernel.org
Subject: git-svn writing mergeinfo
Date: Thu, 11 Feb 2010 11:10:07 -0600 [thread overview]
Message-ID: <20100211111007.b04e8f26.stephen@exigencecorp.com> (raw)
Hi,
I just stumbled across the mergeinfo support coming in git 1.7. Looks
like very awesome stuff for those of us using git as a better-than-svn
svn client.
Trying 1.7-rc2 locally, I can see mergeinfo properties getting read.
But the killer feature of doing a git merge --no-ff/git svn dcommit
doesn't seem to generate and write mergeinfo properties back to svn.
Unless I'm doing something wrong.
Are there any plans for this, even if svn's model means only in
a limited form? E.g. no multi-parent/reflective/etc.
I was really surprised to learn that Bazaar writes mergeinfo back to
svn [1]--I had assumed a DAG-based DVCS would just never get that good
of svn interop. So, seeing that Bazaar does something like this gives
me hope that git could do it eventually as well.
Thanks,
Stephen
[1]: http://wiki.bazaar.canonical.com/BzrForeignBranches/Subversion
reply other threads:[~2010-02-11 17:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100211111007.b04e8f26.stephen@exigencecorp.com \
--to=stephen@exigencecorp.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).