From kde-scm-interest  Wed Jan 14 23:11:35 2009
From: Robert Wohlrab <robert.wohlrab () gmx ! de>
Date: Wed, 14 Jan 2009 23:11:35 +0000
To: kde-scm-interest
Subject: Re: [Kde-scm-interest] Accountability, concrete suggestion
Message-Id: <200901150011.36279.robert.wohlrab () gmx ! de>
X-MARC-Message: https://marc.info/?l=kde-scm-interest&m=123197474718674

> > 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.
>
> Just to note that this "commit annotations" are already in the next
> branch of git.git and are called git notes:
>
> http://git.kernel.org/?p=git/git.git;a=commit;h=bf4d571fc001337cf42add1126c
>c249bb5662815
>
> and possibly will be available with the next major version.
Just for clarification:
- We must write our own tool create annotations which signs the commits in 
some way?
- We want that the actual commiter (not the author of the patch) signs all 
commits with such a note?
- a note is only a tag object which points to a commit and no else first class 
git object (commit, tag, tree, blob) points to the note?
- the only reference to the note is stored in refs/* or packed-refs (so it is 
only referenced by a ref)?
- we will get an extrem big packed-refs when we really add a note to every 
commit?
- No history is stored for a note?
- a note can be overriden?
- An update for a note will automatically downloaded by a pull?

And can a commit have multiple notes?
Is their a good design document with use cases available somewhere?
-- 
Robert Wohlrab
_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest