Re: [RFC] GIT Repository Annotation Convention

2005-09-09 Thread A Large Angry SCM
Junio C Hamano wrote: A Large Angry SCM <[EMAIL PROTECTED]> writes: Junio C Hamano wrote: A Large Angry SCM <[EMAIL PROTECTED]> writes: Naming and Directory Structure -- Annotations are named by appending ".txt" to the basename of the repository component it descr

Re: [RFC] GIT Repository Annotation Convention

2005-09-08 Thread A Large Angry SCM
Junio C Hamano wrote: A Large Angry SCM <[EMAIL PROTECTED]> writes: Naming and Directory Structure -- Annotations are named by appending ".txt" to the basename of the repository component it describes, and by appending ".dir" to each directory patch component leading

Re: [RFC] GIT Repository Annotation Convention

2005-09-08 Thread A Large Angry SCM
Chuck Lever wrote: yay! are you also proposing some git tools to deal with these? it would be great to have some version control (keep these like generation files so we can see the history of revisions). A Large Angry SCM wrote: GIT Repository Annotation Convention [...] I'm not proposing

Re: [RFC] GIT Repository Annotation Convention

2005-09-08 Thread Junio C Hamano
A Large Angry SCM <[EMAIL PROTECTED]> writes: > Naming and Directory Structure > -- > Annotations are named by appending ".txt" to the basename of the > repository component it describes, and by appending ".dir" to each > directory patch component leading to the reposit

[RFC] GIT Repository Annotation Convention

2005-09-08 Thread A Large Angry SCM
GIT Repository Annotation Convention GIT repositories can benefit from descriptions of /intent/ for portions of the repository. This document formalizes a method to store those descriptions in the repository. Annotations Annotations are UTF8 text