From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Eric Van Hensbergen" <ericvh@gmail.com>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] bug fixes for 9p linux-2.6.28-rc4
Date: Mon, 17 Nov 2008 08:32:47 -0800 [thread overview]
Message-ID: <20081117083247.8b91e965.randy.dunlap@oracle.com> (raw)
In-Reply-To: <a4e6962a0811151228h14679d35m56eceff433e518f9@mail.gmail.com>
On Sat, 15 Nov 2008 14:28:45 -0600 Eric Van Hensbergen wrote:
> sorry - just cut n' pasted the output of git-request-pull, didn't
> notice it didn't tag on a diffstat, maybe I have an old buggy version
> of git.
>
> -eric
>
>
> On Sat, Nov 15, 2008 at 1:40 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> >
> > On Fri, 14 Nov 2008, Eric Van Hensbergen wrote:
> >>
> >> The following changes since commit 4ff429e658c00bcf5101eabbebd4f711572a64cb:
> >> Randy Dunlap (1):
> >> 9p: restrict RDMA usage
> >>
> >> are available in the git repository at:
> >>
> >> ssh://master.kernel.org/pub/scm/linux/kernel/git/ericvh/v9fs.git for-linus
> >
> > Diffstat?
> >
> > Yeah, I see that it is
> >
> > net/9p/Kconfig | 10 ++++++----
> > 1 files changed, 6 insertions(+), 4 deletions(-)
> >
> > but I want to know things like that _before_ pulling, just to know what to
> > expect, and so that I know that what I pull is what you meant me to pull.
Eric,
See Documentation/SubmittingPatches: 16) Sending "git pull" requests
It details the pull request and the expected diffstat.
---
~Randy
prev parent reply other threads:[~2008-11-17 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 22:25 Eric Van Hensbergen
2008-11-15 19:40 ` Linus Torvalds
2008-11-15 20:28 ` Eric Van Hensbergen
2008-11-17 16:32 ` Randy Dunlap [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=20081117083247.8b91e965.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=ericvh@gmail.com \
--cc=linux-kernel@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®