From kde-scm-interest Wed Aug 06 09:47:42 2008 From: "=?ISO-8859-1?Q?Santi_B=E9jar?=" Date: Wed, 06 Aug 2008 09:47:42 +0000 To: kde-scm-interest Subject: Re: [Kde-scm-interest] Accountability, concrete suggestion Message-Id: <8aa486160808060247j6b6e36ffu968a530392cdbc7c () mail ! gmail ! com> X-MARC-Message: https://marc.info/?l=kde-scm-interest&m=121801612623727 Thiago Macieira wrote: >Patrick Aljord wrote: >>On Fri, Aug 1, 2008 at 5:39 PM, Thiago Macieira wrote: >>>meaning all you need are the commands git-commit-tree and >>> git-update-ref. >> >>That sounds great Thiago. I'll give it a try and see what I can do. >>Unless you already have a script for that, don't hesitate to post it >>here :) > >No, it's all in my head for the moment. I have a high priority task that I >have to finish for Qt 4.5, but when I'm done, I plan on dedicating a week >to our internal conversion to Git. This will give me time to work on the >Hook scripts like this. I think that these annotations can be done with "commits annotations", the "conts" is that it is not currently supported in git.git, but it seams there are a few people interested in it. The last "status report" that I've found is: http://article.gmane.org/gmane.comp.version-control.git/83732 Another possibility is to reuse the current reflogs format but keep them in the logging branch. I think the trust network (ala Linus) can work also in KDE. Yes, KDE has a lot of committers, but the only extra thing in KDE is the traceability of who pushed the changes to the KDE servers. So, it should be clear that the committer and author fields are only informational, the important thing for the accountability is the "pusher". It also happens in svn, when you say in the commit message that you applied a patch from somebody else, but then it was the committer and with DSCM are the pushers. Santi _______________________________________________ Kde-scm-interest mailing list Kde-scm-interest@kde.org https://mail.kde.org/mailman/listinfo/kde-scm-interest