From: Jeff Garzik <jeff@garzik.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net,
nfsv4@linux-nfs.org
Subject: Re: [GIT] NFS client update for 2.6.16
Date: Tue, 21 Mar 2006 12:50:56 -0500 [thread overview]
Message-ID: <44203D00.4030507@garzik.org> (raw)
In-Reply-To: <1142961077.7987.14.camel@lade.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 529 bytes --]
Trond Myklebust wrote:
> Hi Linus,
>
> Please pull from the repository at
>
> git pull git://git.linux-nfs.org/pub/linux/nfs-2.6.git
>
> This will update the following files through the appended changesets.
It would IMO be nice if you would pipe the changelog through 'git
shortlog', to better summarize the submission. And if the cumulative
patch isn't over 100k or so, include that in the email for any last
minute review.
I've attached the simple script I use to generate pull emails for
Andrew/Linus...
Jeff
[-- Attachment #2: mkmsg.sh --]
[-- Type: application/x-shellscript, Size: 485 bytes --]
next prev parent reply other threads:[~2006-03-21 17:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 17:11 [GIT] NFS client update for 2.6.16 Trond Myklebust
2006-03-21 17:46 ` [NFS] " Christoph Hellwig
2006-03-21 18:03 ` Chuck Lever
2006-03-21 18:55 ` Christoph Hellwig
2006-03-21 18:08 ` Trond Myklebust
2006-03-21 18:57 ` Christoph Hellwig
2006-03-21 19:06 ` Trond Myklebust
2006-03-21 19:12 ` Chuck Lever
2006-03-22 10:30 ` Christoph Hellwig
2006-03-22 11:35 ` Trond Myklebust
2006-03-21 18:58 ` Trond Myklebust
2006-03-22 10:25 ` Christoph Hellwig
2006-03-21 17:50 ` Jeff Garzik [this message]
2006-03-21 18:12 ` Trond Myklebust
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=44203D00.4030507@garzik.org \
--to=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4@linux-nfs.org \
--cc=torvalds@osdl.org \
--cc=trond.myklebust@fys.uio.no \
/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