linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: John Spencer <maillist-lvm@barfooze.de>
To: zkabelac@redhat.com, agk@redhat.com
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm2 portability issues (GNU sed is assumed)
Date: Tue, 19 Mar 2013 18:38:54 +0100	[thread overview]
Message-ID: <5148A2AE.7030405@barfooze.de> (raw)
In-Reply-To: <512A2DC3.6040503@barfooze.de>

On 02/24/2013 04:12 PM, John Spencer wrote:
> On 01/31/2013 04:31 AM, John Spencer wrote:
>> On 01/30/2013 03:55 AM, Alasdair G Kergon wrote:
>>> On Tue, Jan 29, 2013 at 08:51:21PM +0100, John Spencer wrote:
>>>> may i ask kindly to reformulate that statement so that it works with
>>>> posix sed (as used in busybox 1.20.2) ?
>>>
>>> I'm perfectly happy using modern extensions to these tools:)
>>>
>>> If you want this to work with alternative versions, please send a tested
>>> patch for us to incorporate. (Either modifications to the commands so
>>> it works with both or else alternative versions which configure chooses
>>> between.)
>>
>> a couple of regex experts looked at it, and the reason it didnt work is
>> simply a bug: the \ before d is wrong. apparently the author meant to
>> escape the makefile variable that follows, but that is not necessary and
>> so the backslash gets passed on.
>>
>> find attached a patch that works correctly with gnu sed and busybox sed.
>
>
> zdenek, since alasdair does not seem to react, would you mind applying
> this patch for a quick test, see that it generates both linker scripts
> (.export.sym) correctly (exactly the same output than before) and merge
> it ? thanks!
>
> (reattaching the patch)
>
> thanks,
> --JS
>

ping

      reply	other threads:[~2013-03-19 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 19:51 [linux-lvm] lvm2 portability issues (GNU sed is assumed) John Spencer
2013-01-30  2:55 ` Alasdair G Kergon
2013-01-31  3:31   ` John Spencer
2013-02-24 15:12     ` John Spencer
2013-03-19 17:38       ` John Spencer [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=5148A2AE.7030405@barfooze.de \
    --to=maillist-lvm@barfooze.de \
    --cc=agk@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=zkabelac@redhat.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).