From: Junio C Hamano <junkio@cox.net>
To: jgarzik@pobox.com, torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [OT] pull request notation
Date: Tue, 24 May 2005 17:59:46 -0700 [thread overview]
Message-ID: <7vll64rugt.fsf@assigned-by-dhcp.cox.net> (raw)
>>>>> "JG" == Jeff Garzik <jgarzik@pobox.com> writes:
JG> Please pull the 'new-ids' branch from
JG>
JG> rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
JG>
JG> This add...
I am not a kernel developer, but I think the way this particular
pull request is worded can be made much more friendly to Cogito
users (that probably is the rest of the world except you, me and
Linus ;-). They use URL fragment notation to express the branch
head, like this:
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git#new-ids
At least for me, eyes always skip to the "rsync://..." part
immediately after seeing "Please pull.." part.
For Linus I am willing to volunteer updating git-pull-script to
take the same URL fragment notation, but as Jeff correctly
pointed out it already takes the "branch" name as its second
parameter so it probably would not be necessary.
next reply other threads:[~2005-05-25 0:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 0:59 Junio C Hamano [this message]
2005-05-26 2:40 ` [OT] pull request notation Jeff Garzik
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=7vll64rugt.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox