public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Al Viro <viro@ftp.linux.org.uk>,
	linux-kernel@vger.kernel.org,
	linux1394-devel@lists.sourceforge.net,
	Ben Collins <bcollins@ubuntu.com>,
	Jody McIntyre <scjody@modernduck.com>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [git pull] ieee1394 tree for 2.6.18
Date: Tue, 20 Jun 2006 20:34:22 +0100	[thread overview]
Message-ID: <20060620193422.GA10748@flint.arm.linux.org.uk> (raw)
In-Reply-To: <44984CA1.5010308@s5r6.in-berlin.de>

On Tue, Jun 20, 2006 at 09:29:37PM +0200, Stefan Richter wrote:
> Russell King wrote:
> >On Mon, Jun 19, 2006 at 08:14:45PM -0700, Linus Torvalds wrote:
> >>I want them to tell me what they are sending, so that _when_ I pull, I 
> >>can line up the result of that pull with the mail they sent, and I can 
> >>tell "ok, that's actually what the other side intended".
> >
> >Given that you've complained about me sending daily pull requests
> >already, how do you intend folk to handle the situation where they've
> >sent you a pull request, it's apparantly been ignored, and they update
> >the tree from which you pull (maybe for akpm's benefit) and then you
> >eventually get around to pulling it a couple of days later?
> [...]
> 
> I don't maintain git repos myself, but I'd say _branches_ or something 
> like that might be the way to go.

The point was to try to establish when we could consider the tree from
which we'd asked Linus to pull from as being sufficiently old that it
would not be pulled from without another request being sent - or if it
was pulled from, that we wouldn't get an email from Linus about the fact
there was new stuff in there.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2006-06-20 19:34 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-18 12:03 [git pull] ieee1394 tree for 2.6.18 Stefan Richter
2006-06-20  2:06 ` Linus Torvalds
2006-06-20  2:55   ` Al Viro
2006-06-20  3:14     ` Linus Torvalds
2006-06-20  4:22       ` Al Viro
2006-06-20  4:31         ` Al Viro
2006-06-20  4:35           ` Roland Dreier
2006-06-20 17:53       ` Russell King
2006-06-20 19:29         ` Stefan Richter
2006-06-20 19:34           ` Russell King [this message]
2006-06-20 20:02             ` Dave Neuer
2006-06-20 20:22               ` Al Viro
2006-06-20 21:15                 ` Dave Neuer
2006-06-20 21:40                   ` Linus Torvalds
2006-06-20 20:57             ` Stefan Richter
2006-06-20 21:03               ` Stefan Richter
2006-06-20 21:15               ` Al Viro
2006-06-21 17:08                 ` Ryan Anderson
2006-06-20 21:25         ` Linus Torvalds
2006-06-20 10:38   ` Stefan Richter
2006-06-21  3:07     ` Linus Torvalds
2006-06-21  6:32       ` Ben Collins
2006-06-21  9:49         ` Stefan Richter
2006-06-21 10:27           ` Ben Collins
2006-06-21 12:01           ` Junio C Hamano

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=20060620193422.GA10748@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=bcollins@ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=scjody@modernduck.com \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=torvalds@osdl.org \
    --cc=viro@ftp.linux.org.uk \
    /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