From: Michael J Gruber <git@drmicha.warpmail.net>
To: Graeme Geldenhuys <graemeg@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git svn graft-branches
Date: Fri, 17 Jul 2009 16:21:57 +0200 [thread overview]
Message-ID: <4A608905.8070705@drmicha.warpmail.net> (raw)
In-Reply-To: <h3pn45$eam$1@ger.gmane.org>
Graeme Geldenhuys venit, vidit, dixit 17.07.2009 13:25:
> Hi,
>
> Looking at the history of a cloned SubVersion repository, I noticed that
> git does track svn merges between the subversion branches.
>
> Apparently there was a command to help git detect this merge:
>
> git-svn graft-branches
>
> As documented in the URL below
>
> http://www.kernel.org/pub/software/scm/git/docs/v1.5.0.7/git-svn.html
>
>
> Now I have git version 1.6.3.3.363.g725cf7 but if I run the following,
> git simply shows the help, and graft-branches doesn't seem to be a
> command anymore. Was 'graft-branches' removed from Git?
>
> $ git svn graft-branches
>
> Above does not work anymore.
$git log -Sgraft-branches
commit a836a0e1729d1758b4085cd07fc79cb9acb64908
Author: Eric Wong <normalperson@yhbt.net>
Date: Wed Feb 14 19:34:56 2007 -0800
git-svn: documentation updates for new functionality
Force the showing of the --minimize flag as an option in the
'migrate' help.
Also, fix the usage function to correctly filter out
the deprecated aliases.
Signed-off-by: Eric Wong <normalperson@yhbt.net>
commit d05d72e07e49869fe988d4d99e6ac60711570db5
Author: Eric Wong <normalperson@yhbt.net>
Date: Mon Jan 15 22:59:26 2007 -0800
git-svn: remove graft-branches command
It's becoming a maintenance burden. I've never found it
particularly useful myself, nor have I heard much feedback about
it; so I'm assuming it's just as useless to everyone else.
Signed-off-by: Eric Wong <normalperson@yhbt.net>
...
prev parent reply other threads:[~2009-07-17 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 11:25 git svn graft-branches Graeme Geldenhuys
2009-07-17 14:21 ` Michael J Gruber [this message]
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=4A608905.8070705@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=graemeg@gmail.com \
/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).