Stefano Zacchiroli wrote:
> Then, while we are at it, I've an extra remark on the README.source
> steps (kind of related to this bug report, as they are basically an
> "API" to use the snippet). We currently say:
>
>> 5. Update the branch (if needed):
>> git add -f -u
>> git add -f debian/patches
>> git commit "Releasing ${VERSION}"
Actually, this is in my README.source, so don't blame Martin ;-)
> but strictly speaking the commit message is wrong. debian/patches/ do
> not necessarily change at each release, neither upstream, neither
> debian-specific (especially when you are lucky). That message should
> actually reflect what has been done which required regenerating
> debian/patches/. Comments?
Sure. Maybe a more detailed message (something similar to what git-dch
adds to debian/changelog) would prove helpful. I still don't have any
idea on what should be the (one-line) patch title, though.
--
Stéphane
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
