From: Kyle Moffett <mrmacman_g4@mac.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Git training wheels for the pimple faced maintainer
Date: Fri, 20 Oct 2006 02:35:19 -0400 [thread overview]
Message-ID: <D6DF81E5-B51F-47D2-AA02-9EBD63FD6D6B@mac.com> (raw)
In-Reply-To: <45386C29.7050501@drzeus.cx>
On Oct 20, 2006, at 02:26:49, Pierre Ossman wrote:
> Andrew Morton wrote:
>> Just send me the url&branch-name for a tree which you want
>> included in -mm.
>> I typically pull all the trees once per day. I usually won't even
>> look at
>> the contents of what I pulled from you unless it breaks.
>>
>> IOW, -mm is like a tree to which 70-odd people have commit
>> permissions,
>> except it's 70 separate trees and I independently jam them all
>> into one
>> tree daily.
>>
>
> So, in other words, you have no issues with a lot of merges in the
> branch you're pulling from? Do you do a fresh pull each time or do
> you update an existing copy? If you do the latter, then I assume it
> is critical that my "for-andrew" branch has a continous history?
> (Which it won't naturally have as the changes will be replaced by
> identical changes coming from Linus' tree)
I seem to remember Andrew saying something like (paraphrased) "In the
event that your tree doesn't have a continuous history for whatever
reason, I'll just pull a fresh copy and work from there". Given that
he maintains -mm as a quilt patchset and only uses GIT for incoming
pulls, I would guess that either way is probably OK, although the
continuous history makes merging and fixing rejects mildly nicer.
Cheers,
Kyle Moffett
next prev parent reply other threads:[~2006-10-20 6:35 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 [this message]
2006-10-20 6:37 ` Andrew Morton
2006-10-25 21:50 ` Pierre Ossman
2006-10-25 22:06 ` Andrew Morton
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=D6DF81E5-B51F-47D2-AA02-9EBD63FD6D6B@mac.com \
--to=mrmacman_g4@mac.com \
--cc=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
all inboxes | Powered by JetHome®