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 20:51:55 +0200	[thread overview]
Message-ID: <f9d3ce$1lo$1@sea.gmane.org> (raw)
In-Reply-To: <7vy7gm4cdv.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:
> Parents' order and which branch you are on may not have anything
> to do with each other.  Somebody else may have pulled a while on
> b, and you might have pulled from him the merge he created by
> doing so while you are on branch a.
> 

You're right, I didn't think of that. While pondering this I came up 
with another problem: git-svn currently remembers which svn-branch a 
commit belongs to by including this information in the git commit log 
message.
This way it is not possible to have one git-commit appear in more than 
one svn branch. Maybe it's better to store this git-commit->svn-branch 
mapping somewhere else. Although it's probably even better to completely 
switch to git :)

Matthias

  reply	other threads:[~2007-08-08 18:52 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
2007-08-08  9:13     ` Junio C Hamano
2007-08-08 18:51       ` Matthias Kleine [this message]
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='f9d3ce$1lo$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.