From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Ilari Liusvaara <ilari.liusvaara@elisanet.fi>,
Daniel Barkalow <barkalow@iabervon.org>,
Gabriel Filion <lelutin@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH v9] Documentation/remote-helpers: Add invocation section
Date: Thu, 8 Apr 2010 00:03:24 -0500 [thread overview]
Message-ID: <20100408050323.GA5987@progeny.tock> (raw)
In-Reply-To: <x2of3271551004072154r62d10023r32e74064d38aff75@mail.gmail.com>
Ramkumar Ramachandra wrote:
> Can I see the topic branch corresponding to my patches? If this is
> possible, I can avoid the more painful procedure of extracting it from
> the latest pu using git-resurrect.sh.
I tend to do the extraction by hand:
1. git log --first-parent origin/pu
2. Search for "rr/".
3. git branch -f rr/whatever <relevant sha1>
Maybe it would be nice to have a script that does just that instead of
the more costly "git resurrect -m rr/whatever".
Cheers,
Jonathan
next prev parent reply other threads:[~2010-04-08 5:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 5:57 [PATCH v9] Documentation/remote-helpers: Add invocation section Ramkumar Ramachandra
2010-04-07 8:56 ` Ramkumar Ramachandra
2010-04-07 15:05 ` Junio C Hamano
2010-04-07 16:50 ` Ramkumar Ramachandra
2010-04-07 17:23 ` Junio C Hamano
2010-04-07 17:58 ` Ramkumar Ramachandra
2010-04-07 22:49 ` Jonathan Nieder
2010-04-07 23:02 ` Junio C Hamano
2010-04-08 4:54 ` Ramkumar Ramachandra
2010-04-08 5:03 ` Jonathan Nieder [this message]
2010-04-08 5:14 ` Junio C Hamano
2010-04-10 12:24 ` Ramkumar Ramachandra
2010-04-08 18:52 ` Sverre Rabbelier
2010-04-08 20:01 ` Re*: " Junio C Hamano
2010-04-08 20:21 ` Sverre Rabbelier
2010-04-08 20:45 ` Junio C Hamano
2010-04-09 2:06 ` Michael J Gruber
2010-04-10 4:59 ` Junio C Hamano
2010-04-10 12:36 ` Ramkumar Ramachandra
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=20100408050323.GA5987@progeny.tock \
--to=jrnieder@gmail.com \
--cc=artagnon@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ilari.liusvaara@elisanet.fi \
--cc=lelutin@gmail.com \
--cc=srabbelier@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).