Hi Brian,

Brian Gernhardt schrieb am Mon 28. Apr, 15:13 (-0400):
quoted text
> This loop-reverse-loop construct is _extremely_ ugly, and I'm having =20
> problems following it.  None of what this function is doing is =20
> immediately obvious.  It's a good candidate for a comment or two.

I write one.

quoted text
> I also dislike the large lists this is carrying around in shell =20
> variables.  If I'm reading it correctly, the tag list could be replaced=
=20
quoted text
> by invocations of "git describe --exact-match".

Yes. How to get all tags of a commit?

% git tag foo v1.5.5
% git describe --exact-match 9d831805195ba40b62f632acc6bb6e53d3
warning: tag 'v1.5.5' is really 'foo' here
v1.5.5

quoted text
> Now that I think about it, the generation of marks could be done by a =20
> second loop over the list.  Notice what commits need to be marked in =20
> loop 1, then add the mark commands in loop 2.  Both of these loops would=
=20
quoted text
> function in the same direction, removing the need for either tac or perl.

You are right.

Thanks for your comments.

Bye, J=F6rg.
--=20
Damit das M=F6gliche entsteht, mu=DF immer wieder das Unm=F6gliche versucht
werden.                                       (Hermann Hesse)