From: Paul Jackson <pj@sgi.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: akpm@osdl.org, blaisorblade_spam@yahoo.it, linux-kernel@vger.kernel.org
Subject: Re: Inclusion of UML in 2.6.8
Date: Sat, 26 Jun 2004 23:32:53 -0700 [thread overview]
Message-ID: <20040626233253.06ed314e.pj@sgi.com> (raw)
In-Reply-To: <20040627035923.GB8842@ccure.user-mode-linux.org>
> I'm looking at quilt
Good tool.
It's a bit like a loaded gun with no safety. You will learn a few new
ways to shoot your foot off, and become good at first aid. You will
want someway to keep personal revision history of your patches, to aid
in such repair work. CVS or RCS or local bitkeeper or (for ancient
hackers like me) raw SCCS or some such. Quilt handles the patches, but
in and of itself has nothing to do with preserving history.
All software is divided into two parts - the concrete and the fluid.
Once something is accepted into the main kernel, it's concrete. You can
never go back - you can only layer fixes on top. Bitkeeper rules for
this stuff.
But work in progress, for which oneself is still the primary source, is
fluid. You can slice and dice and redo it, and indeed you want to, to
get the best patch set. Quilt and friends rule for this stuff.
Conclusion - use Quilt (with your favorite personal version control) on
top of Bitkeeper.
Question - what tools are available for convenient patch set submission?
Composing multiple, related email sets in a GUI emailer is a bit tedious
and error prone. It's an obvious candidate for scripting.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-06-27 6:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 17:05 Inclusion of UML in 2.6.8 BlaisorBlade
2004-06-26 18:10 ` Christoph Hellwig
2004-06-27 3:53 ` Jeff Dike
2004-06-27 13:57 ` Rik van Riel
2004-06-28 10:55 ` Arnd Bergmann
2004-06-29 19:29 ` Uploaded Uml patchset for 2.6.7(was: Re: Inclusion of UML in 2.6.8) BlaisorBlade
2004-07-03 18:25 ` [uml-devel] " BlaisorBlade
2004-06-26 20:09 ` Inclusion of UML in 2.6.8 Andrew Morton
2004-06-27 3:59 ` Jeff Dike
2004-06-27 6:32 ` Paul Jackson [this message]
2004-06-27 6:40 ` Andrew Morton
2004-06-27 8:08 ` Paul Jackson
2004-06-27 13:50 ` Andreas Gruenbacher
2004-06-27 23:43 ` Paul Jackson
2004-06-28 21:18 ` David Eger
2004-06-27 8:53 ` Geert Uytterhoeven
[not found] ` <20040628181134.GA21360@havoc.gtf.org>
[not found] ` <Pine.GSO.4.58.0407201754460.23496@waterleaf.sonytel.be>
2004-07-22 13:09 ` [PATCH] cirrusfb: update for amiga (zorro) David Eger
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=20040626233253.06ed314e.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.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