From: "Jörg Sommer" <joerg@alea.gnuu.de>
To: Brian Gernhardt <benji@silverinsanity.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Use perl instead of tac
Date: Wed, 30 Apr 2008 11:02:06 +0200 [thread overview]
Message-ID: <20080430090206.GA21826@alea.gnuu.de> (raw)
In-Reply-To: <04EB077D-CB35-4253-A9EA-2085890C3639@silverinsanity.com>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
Hi Brian,
Brian Gernhardt schrieb am Mon 28. Apr, 15:13 (-0400):
> This loop-reverse-loop construct is _extremely_ ugly, and I'm having
> problems following it. None of what this function is doing is
> immediately obvious. It's a good candidate for a comment or two.
I write one.
> I also dislike the large lists this is carrying around in shell
> variables. If I'm reading it correctly, the tag list could be replaced
> 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
> Now that I think about it, the generation of marks could be done by a
> second loop over the list. Notice what commits need to be marked in
> loop 1, then add the mark commands in loop 2. Both of these loops would
> function in the same direction, removing the need for either tac or perl.
You are right.
Thanks for your comments.
Bye, Jörg.
--
Damit das Mögliche entsteht, muß immer wieder das Unmögliche versucht
werden. (Hermann Hesse)
[-- Attachment #2: Digital signature http://en.wikipedia.org/wiki/OpenPGP --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-04-30 12:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 6:24 Use of tac in git-rebase--interactive Brian Gernhardt
2008-04-27 6:42 ` Jeff King
2008-04-27 6:55 ` [PATCH] Use perl instead of tac Brian Gernhardt
2008-04-28 7:44 ` [PATCH] rebase--interactive: Replace unportable 'tac' by a sed script Johannes Sixt
2008-04-28 8:19 ` Junio C Hamano
2008-04-28 8:58 ` Paolo Bonzini
2008-04-28 9:04 ` Jeff King
2008-04-28 9:11 ` Andreas Ericsson
2008-04-28 11:46 ` [PATCH] Use perl instead of tac Jörg Sommer
2008-04-28 12:58 ` Randal L. Schwartz
2008-04-28 13:12 ` David Symonds
2008-04-28 13:31 ` Paolo Bonzini
2008-04-28 14:11 ` Brian Gernhardt
2008-04-28 14:22 ` Johannes Schindelin
2008-04-28 15:15 ` Jörg Sommer
2008-04-28 17:26 ` Avery Pennarun
2008-04-28 17:34 ` Matthieu Moy
2008-04-28 17:50 ` Brian Gernhardt
2008-04-28 19:13 ` Brian Gernhardt
2008-04-30 9:02 ` Jörg Sommer [this message]
2008-04-30 9:39 ` Jörg Sommer
2008-04-30 16:12 ` Brian Gernhardt
2008-04-30 15:25 ` Brian Gernhardt
2008-05-04 22:13 ` Jörg Sommer
2008-05-06 4:32 ` Brian Gernhardt
2008-04-28 13:46 ` Johannes Schindelin
2008-04-28 14:07 ` Brian Gernhardt
2008-04-28 14:20 ` Johannes Schindelin
2008-04-27 7:33 ` Use of tac in git-rebase--interactive しらいしななこ
2008-04-30 0:25 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080430090206.GA21826@alea.gnuu.de \
--to=joerg@alea.gnuu.de \
--cc=benji@silverinsanity.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).