From kde-scm-interest  Wed Jan 14 23:45:44 2009
From: "Boyd Stephen Smith Jr." <bss () iguanasuicide ! net>
Date: Wed, 14 Jan 2009 23:45:44 +0000
To: kde-scm-interest
Subject: Re: [Kde-scm-interest] Accountability, concrete suggestion
Message-Id: <200901141745.48451.bss () iguanasuicide ! net>
X-MARC-Message: https://marc.info/?l=kde-scm-interest&m=123197674621412
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============2002092971=="

--===============2002092971==
Content-Type: multipart/signed;
  boundary="nextPart4521191.iaqgpBa7sL";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart4521191.iaqgpBa7sL
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 2009 January 14 17:11:35 Robert Wohlrab wrote:
>> > 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=3Dgit/git.git;a=3Dcommit;h=3Dbf4d571fc001337cf4=
2add1126
>>c c249bb5662815
>>
>> and possibly will be available with the next major version.

It does need some more testing. :)

>Just for clarification:
>- We must write our own tool create annotations which signs the commits in
>some way?

Yes.  The notes stuff in git is generic, but it should be useful enough for=
=20
our goals.

>- 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?

Not exactly.  There is a "notes reference", which points to a commit object=
=2E =20
The tree of this commit object is expected to use SHAs as filenames, and th=
e=20
notes are in the blobs attached to the tree.  The filename-SHAs indicate to=
=20
which object the note applies.  (It could be a commit, tree, or blob [which=
=20
might be another note!]).

>- the only reference to the note is stored in refs/* or packed-refs (so it
> is only referenced by a ref)?

The notes themselves are stored as normal blobs.  That is, just like the=20
tracked content of files.

>- we will get an extrem big packed-refs when we really add a note to every
>commit?

Git's delta-compression should keep this down.  But, yes, the full text of=
=20
every note AND it's history is stored.

>- No history is stored for a note?

No.  Notes are stored in a standard "tree" object as standard "blob" object=
s,=20
so (at least in theory) all of git's internal machinery can be brought to=20
bear on them.  (e.g. merges, logs, etc.)

>- a note can be overriden?

The notes ref can be changed.  Notes, like all git blobs, are immutable.  O=
n=20
casual inspection (e.g. in the git log), the note will appear to have=20
changed, but the history will be kept and could be retrieved.

>- An update for a note will automatically downloaded by a pull?

Not sure about this.  Since there is currently only one "notes ref", it's=20
unlikely to be overwritten by pull in the default setup.

>And can a commit have multiple notes?

No, I don't believe so, but I could be wrong.

>Is their a good design document with use cases available somewhere?

Not that I know of, although the patches went through a lot of discussion o=
n=20
the git list.
=2D-=20
Boyd Stephen Smith Jr.                     ,=3D ,-_-. =3D.=20
bss@iguanasuicide.net                     ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-'=20
http://iguanasuicide.net/                      \_/    =20

--nextPart4521191.iaqgpBa7sL
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAklueSwACgkQdNbfk+86fC3O8gCeNBhQt1p60Z37egX+yExCdmrM
LpYAoICGHJlqTD/L4fSkyQsGB3pwJ5a3
=savC
-----END PGP SIGNATURE-----

--nextPart4521191.iaqgpBa7sL--

--===============2002092971==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest

--===============2002092971==--