From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Sat, 04 Aug 2007 00:06:34 GMT
Subject: Re: Help a sed noob
Message-ID: <fcaeb9bf0708031706o3e3f4839t39eca4b64b0aab5d@mail.gmail.com>
In-Reply-To: <7vhcngkx38.fsf@assigned-by-dhcp.cox.net>

Great! Thank you both.

On 8/3/07, Junio C Hamano <gitster@pobox.com> wrote:
> "Nguyen Thai Ngoc Duy" <pclouds@gmail.com> writes:
>
> > There is a construct like this in git-parse-remote.sh which makes
> > busybox ash unhappy:
> >
> >                 sed -ne '/^URL: */{
> >                         s///p
> >                         q
> >                 }' "$GIT_DIR/remotes/$1"
> >
> > It complains about "no previous regexp" while gnu sed is ok. Can
> > anyone explain to me what does "s///p" do? GNU Sed info page says
> > nothing about empty regexp. If I replace it with "s/\(.*\)/\1/p" then
> > I get "URL: " along with the remote path.
>
> Traditionally empty LHS regexp means "the same as last match".
> Replace it with "s/^URL: *//p" and you would be Ok.
>
>


-- 
Duy