From: Junio C Hamano <gitster@pobox•com>
To: "Torsten Bögershausen" <tboegi@web•de>
Cc: git@vger•kernel.org
Subject: Re: [PATCH v3] t9001: avoid not portable '\n' with sed
Date: Tue, 10 Jun 2014 08:38:17 -0700 [thread overview]
Message-ID: <xmqqmwdkai6u.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <5396A618.5040306@web.de> ("Torsten Bögershausen"'s message of "Tue, 10 Jun 2014 08:30:48 +0200")
Torsten Bögershausen <tboegi@web•de> writes:
> I think that V3 explains the difference between POSIX sed and
> gnu sed much better, and does reflect all the comments from
> the list, which otherwise may be lost.
Too late for that as the patch is already in 'next' X-<.
prev parent reply other threads:[~2014-06-10 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 4:07 [PATCH v3] t9001: avoid not portable '\n' with sed Torsten Bögershausen
2014-06-10 5:03 ` Eric Sunshine
2014-06-10 5:55 ` Junio C Hamano
2014-06-10 6:30 ` Torsten Bögershausen
2014-06-10 15:38 ` Junio C Hamano [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=xmqqmwdkai6u.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=tboegi@web$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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