From: Sam Ravnborg <sam@ravnborg.org>
To: Eric Van Hensbergen <ericvh@gmail.com>
Cc: torvalds@osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
V9FS Developers <v9fs-developer@lists.sourceforge.net>
Subject: Re: [GIT PULL] 9p patches for 2.6.24 merge window
Date: Thu, 18 Oct 2007 04:49:27 +0200 [thread overview]
Message-ID: <20071018024927.GA16138@uranus.ravnborg.org> (raw)
In-Reply-To: <a4e6962a0710171619r60bea067u5255657381b2d0a9@mail.gmail.com>
On Wed, Oct 17, 2007 at 06:19:53PM -0500, Eric Van Hensbergen wrote:
> On 10/17/07, Sam Ravnborg <sam@ravnborg.org> wrote:
> > On Wed, Oct 17, 2007 at 04:34:02PM -0500, Eric Van Hensbergen wrote:
> > > Linus, please pull from the 'for-linus' branch of:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/ericvh/v9fs.git/ for-linus
> > >
> > > This tree contains the following:
> > >
> > > Latchesar Ionkov(3):
> > > attach-per-user support
> > > rename uid and gid parameters
> > > define session flags
> > >
> > > Eric Van Hensbergen(4)
> > > remove sysctl code
> > > fix bad kconfig cross-dependency
> > > soften invalidationin loose mode
> > > make transports dynamic
> >
> > Could you please tag your patches with 9p: or [9p] so it
> > is obvious that they belong to this subsystem.
> > When browsing head-commits and other places this is a great help.
> >
>
> They should be so tagged, I just stripped it in my pull email summary.
OK - thanks.
Sam
prev parent reply other threads:[~2007-10-18 2:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 21:34 Eric Van Hensbergen
2007-10-17 21:39 ` Sam Ravnborg
2007-10-17 23:19 ` Eric Van Hensbergen
2007-10-18 2:49 ` Sam Ravnborg [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=20071018024927.GA16138@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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®