From: Andrew Morton <akpm@osdl.org>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Git training wheels for the pimple faced maintainer
Date: Wed, 25 Oct 2006 15:06:22 -0700 [thread overview]
Message-ID: <20061025150622.1fea8f5b.akpm@osdl.org> (raw)
In-Reply-To: <453FDC13.60409@drzeus.cx>
> On Wed, 25 Oct 2006 23:50:11 +0200 Pierre Ossman <drzeus-list@drzeus.cx> wrote:
> Andrew Morton wrote:
> > I don't care what the history is. I fetch the whole thing then generate
> > (you - linus) as a single unified diff then whack it into the patch pile.
> >
>
> How do you handle when I'm a bit after Linus (which will be the case
> most of the time)? Will me doing pulls left and right distrupt this?
>
Nope, that's fine. git gives me a diff which is "things which are in Pierre's
tree but which aren't in Linus's".
Just go ahead and do whatever it is you want to do and don't bother about
-mm. If something goes badly wrong (it probably won't) then we can take a
look at it.
next prev parent reply other threads:[~2006-10-25 22:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 21:17 Pierre Ossman
2006-10-19 22:25 ` Andrew Morton
2006-10-20 6:26 ` Pierre Ossman
2006-10-20 6:35 ` Kyle Moffett
2006-10-20 6:37 ` Andrew Morton
2006-10-25 21:50 ` Pierre Ossman
2006-10-25 22:06 ` Andrew Morton [this message]
2006-10-19 23:44 ` Linus Torvalds
2006-10-20 1:07 ` Mark Fasheh
2006-10-20 6:45 ` Pierre Ossman
2006-10-20 21:08 ` Mark Fasheh
2006-10-20 4:28 ` Kyle Moffett
2006-10-20 6:34 ` Pierre Ossman
2006-10-20 7:30 ` Kyle Moffett
2006-10-20 15:26 ` Linus Torvalds
2006-10-20 15:35 ` Linus Torvalds
2006-10-21 9:44 ` Pierre Ossman
2006-10-21 16:10 ` Linus Torvalds
2006-10-21 18:05 ` Pierre Ossman
2006-10-21 19:07 ` Linus Torvalds
2006-10-21 16:47 ` Roland Dreier
2006-10-21 18:15 ` Pierre Ossman
2006-10-21 21:27 ` Roland Dreier
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=20061025150622.1fea8f5b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome