From: Andreas Schwab <schwab@suse.de>
To: qemu-devel@nongnu.org
Cc: Ryan Harper <ryanh@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] Fix cscope filelist by removing leading ./
Date: Wed, 01 Oct 2008 17:22:17 +0200 [thread overview]
Message-ID: <jey718l4ra.fsf@sykes.suse.de> (raw)
In-Reply-To: <1222873814-32003-1-git-send-email-ryanh@us.ibm.com> (Ryan Harper's message of "Wed, 1 Oct 2008 10:10:14 -0500")
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/'.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2008-10-01 15:22 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 [this message]
2008-10-01 15:29 ` Ryan Harper
2008-10-01 15:36 ` Laurent Desnogues
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=jey718l4ra.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=ryanh@us.ibm.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).