Hi, Thibaut Paumard: > We have a very nice source package format with "3.0 (quilt)".
IMHO this format is very nice if you have some opaque upstream, and a debian/ directory that's under your control. This restriction does not apply to a DVCS like git. Moreover, git already has built-in mechanisms to do all of this. People who are used to otherwise working with git may not see any sense in learning another way of doing essentially the same thing. > If these modifications are stored already in debian/patches, > representing them also in git in the upstream code is a pointless > duplication of the same information. No. The git representation is a strict superset of the information in debian/patches, as it includes patch history that can be actually reasoned about. > Likewise, I can do > git diff debian/1.0.0-1 debian/1.0.0-2 > If this includes a changed patch, the result of this command is a patch-of-a-patch, which I find to be completely unreadable. > and check the changes that will be represented in the source package. If your changes are applied to the git tree instead of being stored in debian/patches, this command will do the exact same thing (other than patch-of-a-patch changes). -- -- Matthias Urlichs
signature.asc
Description: Digital signature
