How to handle Debian patches

[Jesse Keating]

On Fri, 2008-05-16 at 18:54 +0200, Martin Uecker wrote:
> I am not convinced that more technological infrastructure is really
> the solution. Isn't simply the upstream source the right place for
> collaboration?
> 
> IMHO the problem is not, that managing and reviewing  patches in 
> debian or sharing patches with other is distributions is too hard, 
> but that it is *too easy* to introduce changes into Debian, removing 
> all pressure for close cooperation with the upstream project.

Not when upstream is uninterested in the changes (see grub1).  In these
cases I think it's better to create something like a git repo somewhere
that has vendor branches, and each vendor then does their patch work in
said branches.  Other vendors can easily cherry-pick stuff from one
another.

Of course, some upstreams could setup vendor branches in their upstream
source control and accomplish much of the same thing.

-- 
Jesse Keating
Fedora -- Freedom² is a feature!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/vcs-pkg-discuss/attachments/20080516/bf102564/attachment.pgp