From: Eric Wong <normalperson@yhbt.net>
To: Junio C Hamano <junkio@cox.net>
Cc: Adam Roben <aroben@apple.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-svn: Added 'find-rev' command
Date: Sat, 28 Apr 2007 03:50:16 -0700 [thread overview]
Message-ID: <20070428105016.GA11271@muzzle> (raw)
In-Reply-To: <7vbqh9kov9.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> Eric Wong <normalperson@yhbt.net> writes:
>
> > Adam Roben <aroben@apple.com> wrote:
> >> This patch adds a new 'find-rev' command to git-svn that lets you easily
> >> translate between SVN revision numbers and git tree-ish.
> >
> > Looks useful.
> >
> > Acked-by: Eric Wong <normalperson@yhbt.net>
>
> But looks quite wasteful. Why not run "rev-list -v" or
> something instead of running cat-file on revision one-by-one?
Didn't know about "rev-list -v", but I just checked and it still has the
limited-size buffer that --pretty=raw has.
"git-svn log" only runs cat-file if it can't find a git-svn-id: line at
the bottom. (I used log --abbrev-commit --pretty=raw).
Sorry about the premature Ack, I hadn't had my coffee yet at that point
(and now I'm half awake :x)
Adam:
However, since we're not fetching ranges...
You can do $gs->rev_db_get($rev_nr) to easily find a commit given a
revision. Bonus points if this works independently of the current HEAD
so you can look up revision numbers on different branches. (git-svn log
should be made to support this, too)
--
Eric Wong
next prev parent reply other threads:[~2007-04-28 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 18:57 [PATCH] git-svn: Added 'find-rev' command Adam Roben
2007-04-27 19:30 ` Eric Wong
2007-04-28 6:13 ` Junio C Hamano
2007-04-28 10:50 ` Eric Wong [this message]
2007-04-28 19:22 ` Adam Roben
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=20070428105016.GA11271@muzzle \
--to=normalperson@yhbt.net \
--cc=aroben@apple.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).