From: Roland Dreier <rdreier@cisco.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Git training wheels for the pimple faced maintainer
Date: Sat, 21 Oct 2006 14:27:05 -0700 [thread overview]
Message-ID: <ada7iytl5qu.fsf@cisco.com> (raw)
In-Reply-To: <453A63A4.4070506@drzeus.cx> (Pierre Ossman's message of "Sat, 21 Oct 2006 20:15:00 +0200")
> I've actually been using StGIT up until now. But I've started to feel a
> need for sharing my tree, and StGIT isn't really suited for that.
>
> How have you handled collaborative development on stuff that isn't ready
> for Linus yet? Simply sending patches back and forth?
I don't use StGIT for collaborative development. My StGIT branches
are really just patch queues (as the names for-2.6.19 and for-2.6.20
imply). Usually development is just about done before things wind up
in a maintainer tree, so being able to apply updates to patches
already in my tree is more important than fully automated merged (as
native git gives you).
prev parent reply other threads:[~2006-10-21 21:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 21:17 Git training wheels for the pimple faced maintainer 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
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 [this message]
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=ada7iytl5qu.fsf@cisco.com \
--to=rdreier@cisco.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