From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.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: Sat, 10 Apr 2010 17:54:26 +0530 [thread overview]
Message-ID: <z2tf3271551004100524w9b8cf62ck7e889f87b7f2cb8e@mail.gmail.com> (raw)
In-Reply-To: <7vk4si8r02.fsf@alter.siamese.dyndns.org>
Hi,
> $ git log --first-parent --oneline origin/master..origin/pu
>
> and find "Merge branch 'rr/remote-helper-doc'" in the output. The second
> parent of that merge commit (e.g. 6144af5^2 == ad466d1) is the tip of your
> topic. You can verify it with:
>
> $ git log -p origin/master..ad466d1
> $ git checkout -b remote-helper-doc ad466d1
> ... build further on it ...
Thanks for the excellent instructions. I'm just curious: why didn't
you include these instructions in your rewrite of SubmittingPatches?
-- Ram
next prev parent reply other threads:[~2010-04-10 12:25 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
2010-04-08 5:14 ` Junio C Hamano
2010-04-10 12:24 ` Ramkumar Ramachandra [this message]
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=z2tf3271551004100524w9b8cf62ck7e889f87b7f2cb8e@mail.gmail.com \
--to=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=jrnieder@gmail.com \
--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).