[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to cope with patches sanely (Was: State of the project - input needed)

also sprach Theodore Tso <tytso@mit.edu> [2008.01.28.1613 +1100]:
> From: Author O' The Patch <author@example.com>
> Detailed patch description
> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
> This is at the beginning of every single quilt patch, and because of
> this, we can easily important the patch into either a mercurial or git
> repository, while preserving the authorship information of the patch.

Nice, I didn't see this before. This *is* in fact nice and puts
the quilt *format* very high on my list.

> Since we are keeping the patch series under source control, it
> allows us to refine patches, and keep a historical record of the
> improvements to a particular patch before it us pushed upstream.

and I guess you can use feature branches to create the patches, if
you like working with the VCS for this sort of thing (like I do) and
then store them in yet another branch. :)

 .''`.   martin f. krafft <madduck@debian.org>
: :'  :  proud Debian developer, author, administrator, and user
`. `'`   http://people.debian.org/~madduck - http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems
windoze 98: <n.> useless extension to a minor patch release for 32-bit
  extensions and a graphical shell for a 16-bit patch to an 8-bit
  operating system originally coded for a 4-bit microprocessor, written
  by a 2-bit company that can't stand for 1 bit of competition.

Attachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)

Reply to: