All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Kleine <matthias_kleine@gmx.de>
To: git@vger.kernel.org
Subject: Re: git-svn: Finding the svn-URL of the current branch in git
Date: Wed, 08 Aug 2007 10:54:55 +0200	[thread overview]
Message-ID: <f9c0d1$7md$1@sea.gmane.org> (raw)
In-Reply-To: <20070807205543.GB27703@xp.machine.xx>

Peter Baumann wrote:
> 
> I had this situation, too.
> 
> 
> 			a = svn branch 'a'
> 	  m		b = svn branch 'b' (in my case, it was trunk)
>       /   \		m = a merge of branch 'a' and 'b', not yet commited to svn
>      a     b
> 
> So trying to dcommit m, git svn can't figure out on which branch, as 'a'
> and 'b' are both reachable. I had to use a graft file to lose one of the
> parents, which let git-svn commit to SVN.

You're right, both 'a' and 'b' are reachable from 'm'.  But if I got it 
right 'm' also contains information as to which one is the first parent 
and thereby which branch we're on. So wouldn't it be enough, if git-svn 
automatically chose the first parent (using log --first-parent)?

> 
> So for a short fix to get the work done, you could create a graft file
> where you fake m to only have one parent.
>
Thanks for that one. I didn't know about the grafts file before.

Matthias

  reply	other threads:[~2007-08-08  9:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 18:29 git-svn: Finding the svn-URL of the current branch in git Matthias Kleine
2007-08-07 20:55 ` Peter Baumann
2007-08-08  8:54   ` Matthias Kleine [this message]
2007-08-08  9:13     ` Junio C Hamano
2007-08-08 18:51       ` Matthias Kleine
2007-08-08 19:25         ` Peter Baumann
2007-08-08 20:57           ` Peter Baumann
2007-08-16  8:21   ` Eric Wong
2007-08-16 12:16     ` Peter Baumann
2007-08-17  7:55       ` Eric Wong
2007-08-17  8:45     ` Junio C Hamano
2007-08-18  9:09       ` Eric Wong
2007-08-18  9:57         ` David Kastrup
2007-08-18 10:04           ` Junio C Hamano
2007-08-18 21:18             ` Karl Hasselström

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='f9c0d1$7md$1@sea.gmane.org' \
    --to=matthias_kleine@gmx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.