From: Linus Torvalds <torvalds@linux-foundation.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel@vger.kernel.org, Liam Howlett <howlett@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Pull request: TASK_KILLABLE
Date: Tue, 29 Jan 2008 22:41:24 +1100 (EST) [thread overview]
Message-ID: <alpine.LFD.1.00.0801292237480.3505@www.l.google.com> (raw)
In-Reply-To: <20080129000447.GC31101@parisc-linux.org>
On Mon, 28 Jan 2008, Matthew Wilcox wrote:
>
> I'd like you to pull the task_killable branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/willy/misc.git
Well, Andrew already pointed out some of this, but I do want more
information. There's a "git request-pull" script that even comes with git
and that generates a shortlog, a proper url+branch description, and a
diffstat of the changes.
So that is already much more descriptive, but in addition to that, if this
isn't one of the "regular" pulls (which it obviously isn't), I really want
a human description too so that I know what I'm pulling and what it's all
about.
I do *not* want to be in the position of having to fetch first, just to be
able to look at what I'm fetching. By the time I pull a branch, I want to
basically know (a) what I'm pulling and (b) why I _want_ to pull it.
Linus
next prev parent reply other threads:[~2008-01-29 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 0:04 Matthew Wilcox
2008-01-29 11:41 ` Linus Torvalds [this message]
2008-01-31 23:45 ` Matthew Wilcox
2008-02-01 0:48 ` Linus Torvalds
2008-02-01 1:45 ` Trond Myklebust
2008-02-01 1:54 ` Linus Torvalds
2008-02-01 2:03 ` Trond Myklebust
2008-02-01 2:02 ` Andrew Morton
2008-02-06 2:19 ` Matthew Wilcox
2008-02-06 2:33 ` Andrew Morton
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=alpine.LFD.1.00.0801292237480.3505@www.l.google.com \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=howlett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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®