From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jeff Garzik <jeff@garzik.org>
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 13:12:47 -0500 [thread overview]
Message-ID: <1142964767.7987.65.camel@lade.trondhjem.org> (raw)
In-Reply-To: <44203D00.4030507@garzik.org>
On Tue, 2006-03-21 at 12:50 -0500, Jeff Garzik wrote:
> 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.
The cumulative patch in this case is 291k (smaller than usual, but not
insignificant).
In any case, the individual patches and the cumulative patch are
available, as always, from linux-nfs.org. Please see
http://client.linux-nfs.org/Linux-2.6.x/2.6.16/
> I've attached the simple script I use to generate pull emails for
> Andrew/Linus...
Thanks.
Cheers,
Trond
prev parent reply other threads:[~2006-03-21 18:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 17:11 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
2006-03-21 18:12 ` Trond Myklebust [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=1142964767.7987.65.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4@linux-nfs.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
all inboxes | Powered by JetHome®