On 25/03/10 02:08PM, Junio C Hamano wrote:
> Junio C Hamano <gitster@xxxxxxxxx> writes:
>
> > As this topic is designing essentially a new and machine parseable
> > format, we could even unify all three formats into one. For example,
> > the format could be like this:
> >
> > <oid> NUL [<attr>=<value> NUL]...
> >
> > where
>
> (0) "rev-list" that gives only a sequence of "<oid>" for commit-ish,
> as well as "rev-list --boundary", would fall out as a natural
> consequence. Bog-standard "list of commits" would see a
> sequence of "<oid> NUL", while a boundary object would see
> "<oid> NUL boundary=yes NUL".
I had not considered handling the `--boundary` option. It looks like
boundary objects are printed as part of `show_commit()`, so I can adapt
the handling and do something similar to missing objects:
$ git rev-list -z --boundary <rev>
<oid> NUL boundary=yes NUL
This would remain consistent with the unified format.
-Justin
