Re: [RFC] GIT Repository Annotation Convention
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 describes, and by appending ".dir" to each directory patch component leading to the repository component from $GIT_DIR, and by prepending "annotations/" to the annotation pathname. I suspect you can do the same without .dir but only with .txt. Think about a directory containing directories "foo" and "foo.txt": And where do you see foo.txt under $GIT_DIR/ hierarchy? Are you saying I can't name a branch "foo.txt"? Or have the following branches? $GIT_DIR/refs/head/WidgetSoft/Blue $GIT_DIR/refs/head/WidgetSoft/Red $GIT_DIR/refs/head/WidgetSoft.txt/Blue $GIT_DIR/refs/head/WidgetSoft.txt/Red - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [RFC] GIT Repository Annotation Convention
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 to the repository component from $GIT_DIR, and by prepending "annotations/" to the annotation pathname. I suspect you can do the same without .dir but only with .txt. Think about a directory containing directories "foo" and "foo.txt": With ".dir": foo.dir/ ... foo.txt foo.txt.dir/ ... foo.txt.txt Without ".dir": foo/ ... ==> foo.txt ==> foo.txt/ ... foo.txt.txt - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [RFC] GIT Repository Annotation Convention
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 any new tools, just a convention that existing tools or tools that others may create can adopt to provide information to a repositories users. Some existing tools that could use the annotations are: git-branch git-show-branch gitweb There are likely others. Like any other file under $GIT_DIR, these files are not automatically versioned. Rather, each repository maintainer, needs to decide how a repository's meta-data (project meta-meta-data) is tracked or generated. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [RFC] GIT Repository Annotation Convention
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 repository component from > $GIT_DIR, and by prepending "annotations/" to the annotation pathname. I suspect you can do the same without .dir but only with .txt. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
