linux-kernel - Re: Question about Git tree methodology.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <44C53323.2030905@gentoo.org>
Date:	Mon, 24 Jul 2006 21:52:51 +0100
From:	Daniel Drake <dsd@...too.org>
To:	Matt LaPlante <kernel1@...erdogtech.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Question about Git tree methodology.

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/