From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Roland Dreier <rdreier@cisco.com>
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 20:15:00 +0200 [thread overview]
Message-ID: <453A63A4.4070506@drzeus.cx> (raw)
In-Reply-To: <adabqo5lip8.fsf@cisco.com>
Roland Dreier wrote:
> > Other git maintainers may have other hints about how they work. Anybody?
>
> I use StGIT (http://www.procode.org/stgit/) to have sort of a hybrid
> git/quilt workflow. My infiniband.git tree has the following main
> branches (I also keep other topic branches around):
>
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?
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2006-10-21 18:15 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 [this message]
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=453A63A4.4070506@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
--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