On Sat, 25 Jul 2009, Shawn O. Pearce wrote: > Daniel Barkalow <barkalow@xxxxxxxxxxxx> wrote: > > +Commands are given by the caller on the helper's standard input, one per line. > > + > > +'list':: > > + Outputs the names of refs followed by the hex of their values > > + or "@<name>" for symrefs, one per line. After the complete > > + list, outputs a blank line. > > I hate to be a nit, but why this format and not the one that is > produced by `git ls-remote` and the native protocol? I know its > pretty arbitrary either way, but since we already have a history > of using "SHA1 ref\n" why not continue that tradition here? In the VCS protocol, the SHA1 is generally not known when simply listing refs, so I didn't have a useless initial field in that protocol; I just inherited having the line start with the name for this protocol. In any case, I want to be able to support symrefs, so an extension to the tradition is required, but putting @<dest> before the name instead of after is easy enough. -Daniel *This .sig left intentionally blank* -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html