From: Jeff Garzik <jgarzik@pobox.com>
To: Junio C Hamano <junkio@cox.net>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [OT] pull request notation
Date: Wed, 25 May 2005 22:40:00 -0400 [thread overview]
Message-ID: <42953700.4090604@pobox.com> (raw)
In-Reply-To: <7vll64rugt.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
>>>>>>"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.
It's up to Linus really, he's the consumer of these messages.
Given that git-pull-script requires two arguments, URL and optional
branch, it sounds like
'rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
new-ids' would be the best syntax, if it weren't for darned word wrap.
Jeff
prev parent reply other threads:[~2005-05-26 2:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 0:59 [OT] pull request notation Junio C Hamano
2005-05-26 2:40 ` Jeff Garzik [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=42953700.4090604@pobox.com \
--to=jgarzik@pobox.com \
--cc=junkio@cox.net \
--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