From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Correct usages of sed in git-tag for Mac OS X
Date: Sat, 30 Jun 2007 03:03:07 -0400 [thread overview]
Message-ID: <20070630070307.GP32223@spearce.org> (raw)
In-Reply-To: <7vzm2ic4g8.fsf@assigned-by-dhcp.pobox.com>
Junio C Hamano <gitster@pobox.com> wrote:
> "Shawn O. Pearce" <spearce@spearce.org> writes:
>
> > These major Git functions are much more important than
> > saving two or three lines of a simple sed script.
>
> The size of the script does not worry me. The number of sed
> processes originally did, but the old code also had two
> invocations of sed, and I do not think you can implement the
> "strip the header, and then emit ${LINES} lines" behaviour
> without doing them in separate sed anyway, so I think this is
> fine. But it makes me wonder why we are not using awk ;-)
Or perl. ;-)
But the patch I just sent is sane. And it all will hopefully go
away when Carlos has his C version complete and passing the very
large test suite he recently contributed. So not really worth
worrying about now that its working properly.
But yea, I changed the script the way I did to keep the number of sed
processes per tag equal to what we had before. Its not any better,
but its also not any worse and it at least runs on more systems.
--
Shawn.
prev parent reply other threads:[~2007-06-30 7:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 6:42 [PATCH] Correct usages of sed in git-tag for Mac OS X Shawn O. Pearce
2007-06-30 7:00 ` Junio C Hamano
2007-06-30 7:03 ` Shawn O. Pearce [this message]
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=20070630070307.GP32223@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).