also sprach Stefano Zacchiroli <[EMAIL PROTECTED]> [2008.11.12.1320 +0100]: > Following the (good) path of "Closes", it should probably be > something like "[Commit: fed3f3d]". Also, can't it be put inside > the same parentheses than "Closes", as in "(Closes: #7005180, > #7005181; Commit: fed3f3d)".
Sure. > Finally, I missed if the aim is finding something Git-specific or > not, in the latter case the commit ID can be paired via a VCS > identifier, though I acknowledge that it risks to become too heavy > ... Well, don't we have that information in debian/control? :) also sprach James Westby <[EMAIL PROTECTED]> [2008.11.12.1709 +0100]: > You mean > > [fc5473a06be960382582ddbfb40e2a5f824be122] > > don't you? No, why? Short commit IDs are usually enough in Git. also sprach James Vega <[EMAIL PROTECTED]> [2008.11.12.1728 +0100]: > Yes. My changelog is generated from the commit log and is only > present in the final integration branch. You are one step ahead of me, I just haven't had the time to do this yet. :( Anyway, having the information in the file vs. using the blame tool(s) means that we could trivially link it to the VCS web view though, from packages.debian.org. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems "whoever fights monsters should see to it that in the process he does not become a monster. and when you look into an abyss, the abyss also looks into you." - friedrich nietzsche _______________________________________________ vcs-pkg-discuss mailing list email@example.com http://lists.alioth.debian.org/mailman/listinfo/vcs-pkg-discuss