Re: How to cope with patches sanely --> Debian New Maintainers'
On Sat, Feb 09, 2008 at 10:53:55AM +0100, Patrick Schoenfeld wrote:
> (BTW. there is no need to CC me with your answers, I did not ask for
> that as I am subscribed to the list :-)
> On Sat, Feb 09, 2008 at 12:50:46AM +0100, Pierre Habouzit wrote:
> > quilt is way more powerful to refresh patches when a new upstream
> > occurs. It does what it can do best without having mergeing features,
> > that only an advanced SCM can provide anyways.
> That does mean quilt is able to refresh patches on upstream changes, so
> that with luck the maintainer does not have to refresh the patches for
> changes sources himself? That would be quiet nice, however I still fail
> to see why this is a reason to prefer quilts *format* as an *exchange
> format* if quilt itself is not to be used, which is what you say.
Who said quilt itself is not to be used? The point of the discussion is
that we agree on a patch-exchange format, without forcing an
implementation on people. People who like the quilt implementation will
still be able and encouraged to use quilt with it. Others might just
use vi to edit quilt patches, or git, or something else.