From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Dennis Stosberg" <dennis@stosberg.net>, git@vger.kernel.org
Subject: Re: [PATCH] Make t8001-annotate and t8002-blame more portable
Date: Mon, 19 Jun 2006 18:35:39 +0200 [thread overview]
Message-ID: <81b0412b0606190935g67581ebucf172acb36e53b02@mail.gmail.com> (raw)
In-Reply-To: <7v3be218ri.fsf@assigned-by-dhcp.cox.net>
On 6/18/06, Junio C Hamano <junkio@cox.net> wrote:
> > + 'perl -pi -e "s/^1A.*\n$//; s/^3A/99/" file &&
activestate perl again: doesn't work without giving a backup file extension,
like this: perl -pi.bak -e ...
next prev parent reply other threads:[~2006-06-19 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 20:33 [PATCH] Make t8001-annotate and t8002-blame more portable Dennis Stosberg
2006-06-18 20:58 ` Junio C Hamano
2006-06-18 22:06 ` Dennis Stosberg
2006-06-18 22:21 ` Junio C Hamano
2006-06-19 16:35 ` Alex Riesen [this message]
2006-06-19 19:40 ` [PATCH] Fix t8001-annotate and t8002-blame for ActiveState Perl Dennis Stosberg
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=81b0412b0606190935g67581ebucf172acb36e53b02@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=dennis@stosberg.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).