commit IDs in changelog messsages (was: Introductory mail)

[Stefano Zacchiroli]

On Thu, Nov 13, 2008 at 12:54:03PM +0100, Adeodato Simó wrote:
> > 2)	(Closes: #1234567, Commit: git:fba134)
>
> Though I agree with your reasoning here, I find (2) a tad too
> verbose (mostly because of the colon appearing twice, which requires
> two passes from your brain, if you see what I mean).

Agreed, note that it was not meant to be a concrete syntax proposal,
only a proof of concept for highlighting a design principle.

> May I suggest:
>     3) (Closes: #1234567, Vcs-Git:fba134)
> And Vcs-Hg, Vcs-Bzr, and so on. How does that sound?

Actually, that syntax is the one which gives us problem in Vcs-* field
parsing, but that's only because Debian formats are based on RFC822,
which is field-oriented and typically enables only per-field
lookup.

In this case it will not pose any problem as the parsing will be
ad-hoc. I'm not sure I like it, but I don't have better proposals
("Commit-Git" starts to be a bit too long).

Cheers.

-- 
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..|  .  |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/vcs-pkg-discuss/attachments/20081113/be3c54a6/attachment.pgp