Linux NFS development
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux NFS mailing list <linux-nfs@vger.kernel.org>,
	Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Please pull NFS client bugfixes for Linux 3.4...
Date: Wed, 28 Mar 2012 20:17:32 -0700	[thread overview]
Message-ID: <4F73D44C.5090604@panasas.com> (raw)
In-Reply-To: <1332988097.19172.51.camel@lade.trondhjem.org>

On 03/28/2012 07:28 PM, Myklebust, Trond wrote:

> On Wed, 2012-03-28 at 19:20 -0700, Linus Torvalds wrote:
>> On Wed, Mar 28, 2012 at 7:08 PM, Myklebust, Trond
>> <Trond.Myklebust@netapp.com> wrote:
>>>
>>> Sure thing... I wasn't aware of that semantic difference, but I'm quite
>>> happy to add it to my script...
>>
>> Thanks. And I noticed that it's supposed to be "tags/xyz" with a "s".
>>
>> Of course, you might as well just say "xyz" without mentioning the
>> tag[s] part at all, unless you have a branch with the same name and
>> want to explicitly disambiguate.
>>
>>                    Linus
> 
> The reason for adding the 'tags' label originally was precisely because
> I had an identically named branch, and I wanted to be able to send you
> the signed tag instead.
> 
> I've attached the script that I use to generate pull requests just in
> case someone else doesn't have their own version. It should be fairly
> obvious to modify...
> 



That's funny after my 20th time of running the command by hand and
doing a "man git-request-pull" because I can never remember the order
of things, and I always get the URL wrong 3 times, I decided I should write
a script, boom here it is sent on the mailing list.

Thank you Trond for sharing, here is a new user
Boaz

  reply	other threads:[~2012-03-29  3:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29  1:59 [GIT PULL] Please pull NFS client bugfixes for Linux 3.4 Myklebust, Trond
2012-03-29  2:06 ` Linus Torvalds
2012-03-29  2:08   ` Myklebust, Trond
2012-03-29  2:20     ` Linus Torvalds
2012-03-29  2:28       ` Myklebust, Trond
2012-03-29  3:17         ` Boaz Harrosh [this message]
2012-03-29  3:44           ` Linus Torvalds
2012-03-29  4:08             ` Myklebust, Trond
2012-03-29  4:20               ` Linus Torvalds
2012-03-29  4:38                 ` Myklebust, Trond
2012-03-29  4:59                   ` Linus Torvalds

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=4F73D44C.5090604@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=torvalds@linux-foundation.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