From: Daniel Drake <dsd@gentoo.org>
To: Matt LaPlante <kernel1@cyberdogtech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question about Git tree methodology.
Date: Mon, 24 Jul 2006 21:52:51 +0100 [thread overview]
Message-ID: <44C53323.2030905@gentoo.org> (raw)
In-Reply-To: <20060724163145.5819ce7d.kernel1@cyberdogtech.com>
Matt LaPlante wrote:
> Hi all, I've been playing around with setting up a personal git tree
> for kernel patches. I've followed Jeff Garzik's guide, as well as
> some of the kernel.org docs. I have no problem setting it up,
> however I have a question about which method to use for my tree.
> Basically I just want to use it as a method of tracking my own
> trivial patches (and perhaps give maintainers easier access to them).
Quilt is very good at doing this kind of thing.
http://savannah.nongnu.org/projects/quilt
It keeps all your patches in a "patches" subdirectory and makes going
back and fixing previous patches very easy (git makes this quite hard).
You can rsync your patches/ directory to any webserver, and anyone else
can save them in a patches subdirectory and apply them in the same way
(the equivalent of sharing your tree).
Daniel
next prev parent reply other threads:[~2006-07-24 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 20:31 Question about Git tree methodology Matt LaPlante
2006-07-24 20:52 ` Daniel Drake [this message]
2006-07-25 14:26 ` Stefan Richter
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=44C53323.2030905@gentoo.org \
--to=dsd@gentoo.org \
--cc=kernel1@cyberdogtech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.