mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
	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: Thu, 29 Mar 2012 04:08:39 +0000	[thread overview]
Message-ID: <1332994124.30608.5.camel@lade.trondhjem.org> (raw)
In-Reply-To: <CA+55aFyHmQBXw3ik3qv81_3Zp+4r-VUt_TNBs-M19b6Zt7PDeQ@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1920 bytes --]

On Wed, 2012-03-28 at 20:44 -0700, Linus Torvalds wrote:
> On Wed, Mar 28, 2012 at 8:17 PM, Boaz Harrosh <bharrosh@panasas.com> wrote:
> >
> > Thank you Trond for sharing, here is a new user
> 
> Oh, *please* use git pull-request instead. It does a lot of things
> much better, including the diffstat/shortlog and the tag message, none
> of which Trond's does.
> 
>                       Linus

Maybe I'm running an older version of git (Fedora 16 latest update), but
when I do

git request-pull v3.3 git://git.linux-nfs.org/projects/trondmy/linux-nfs.git nfs-for-3.4-1

I get:

                The following changes since commit c16fa4f2ad19908a47c63d8fa436a1178438c7e7:
                
                  Linux 3.3 (2012-03-18 16:15:34 -0700)
                
                are available in the git repository at:
                  git://git.linux-nfs.org/projects/trondmy/linux-nfs.git ..BRANCH.NOT.VERIFIED..
                
                Andy Adamson (4):
                      SUNRPC: add sending,pending queue and max slot to xprt stats
                      NFSv4.1 set highest_used_slotid to NFS4_NO_SLOT
                      NFSv4.1 handle DS stateid errors
                      NFSv4.1 cleanup DS stateid error handling
                
                ....
                lots of shortlog stuff followed by the diffstat.
                ....

and that's all...


I'm pretty sure that a request to pull from "..BRANCH.NOT.VERIFIED.."
would piss you off, which is why I'll stick to my script for now. It
already has a '-s' option to give you the shortlog, and it will give you
the diffstat by default. All it is missing is the tag message...

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com

ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

  reply	other threads:[~2012-03-29  4:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29  1:59 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
2012-03-29  3:44           ` Linus Torvalds
2012-03-29  4:08             ` Myklebust, Trond [this message]
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=1332994124.30608.5.camel@lade.trondhjem.org \
    --to=trond.myklebust@netapp.com \
    --cc=bharrosh@panasas.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

all inboxes | Powered by JetHome®