From: "Laurent Desnogues" <laurent.desnogues@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix cscope filelist by removing leading ./
Date: Wed, 1 Oct 2008 17:36:29 +0200 [thread overview]
Message-ID: <761ea48b0810010836l333ff216v6d47b2c93eda8cf3@mail.gmail.com> (raw)
In-Reply-To: <20081001152929.GC31395@us.ibm.com>
On Wed, Oct 1, 2008 at 5:29 PM, Ryan Harper <ryanh@us.ibm.com> wrote:
> * Andreas Schwab <schwab@suse.de> [2008-10-01 10:23]:
>> Ryan Harper <ryanh@us.ibm.com> writes:
>>
>> > - find . -name "*.[ch]" -print > ./cscope.files
>> > + find . -name "*.[ch]" -print | sed 's,./,,' > ./cscope.files
>>
>> This will also match 'a/'.
>
> Is there a case where the find command we're using would output
> something without './' in the first to characters in each line where
> that case would be an issue?
Why not using sed 's,^\./,,'?
Laurent
next prev parent reply other threads:[~2008-10-01 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 15:10 [Qemu-devel] [PATCH] Fix cscope filelist by removing leading ./ Ryan Harper
2008-10-01 15:22 ` Andreas Schwab
2008-10-01 15:29 ` Ryan Harper
2008-10-01 15:36 ` Laurent Desnogues [this message]
2008-10-01 21:45 ` Aurelien Jarno
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=761ea48b0810010836l333ff216v6d47b2c93eda8cf3@mail.gmail.com \
--to=laurent.desnogues@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).