From: Al Viro <viro@ftp.linux.org.uk>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
Linus Torvalds <torvalds@osdl.org>,
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 22:15:24 +0100 [thread overview]
Message-ID: <20060620211524.GU27946@ftp.linux.org.uk> (raw)
In-Reply-To: <44986126.506@s5r6.in-berlin.de>
On Tue, Jun 20, 2006 at 10:57:10PM +0200, Stefan Richter wrote:
> Russell King wrote:
> >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.
>
> You could /a/ try to come to an agreement with him about a less brittle
> protocol, or /b/ think of your mail as an "announcement" rather than a
> "request" (for your peace of mind) and follow up with a repost of the
> announcement if you come to know that your updates did not appear in
> Linus' tree when the end of a merge window is near.
c) no matter how badly your variant of git might suck, on server you
can always do
echo [commit-ID] > .git/refs/heads/for-linus-<date>
and ask him to pull that branch from that server (if your version of
git doesn't suck, git checkout -b for-linus-<date>; git checkout <your
previous branch> will do it).
Then move on with the life, using whatever you are using. The question when
to remove that file... hell, run "trim the stuff more than month old"
from cron every month and forget about it.
next prev parent reply other threads:[~2006-06-20 21:15 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
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 [this message]
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=20060620211524.GU27946@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=akpm@osdl.org \
--cc=bcollins@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=scjody@modernduck.com \
--cc=stefanr@s5r6.in-berlin.de \
--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