From: Chuck Ebbert <76306.1226@compuserve.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel source tree splitting
Date: Thu, 1 May 2003 12:00:59 -0400 [thread overview]
Message-ID: <200305011202_MC3-1-36E2-1D26@compuserve.com> (raw)
> But whilst you're waiting, hardlink everything together, and
> patch the differences (patch knows how to break hardlinks).
I don't trust that approach -- too easy to screw up.
> Make a script that cp -lR's the tree to another copy (normally
> takes < 1s), and then remove the other arches. grep that.
That could work for the reference tree.
> cscope with prebuilt indeces on a filtered subset of the files may well do
> better than grep, depending on exactly what you're doing (does 99% of it
> for me).
Have you tried lxr? The website is cool but you really need a local
copy for speed.
------
Chuck
next reply other threads:[~2003-05-01 15:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 16:00 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-01 11:54 Chuck Ebbert
2003-05-01 14:06 ` Martin J. Bligh
2003-05-01 14:20 ` Willy TARREAU
2003-05-01 14:35 ` Martin J. Bligh
2003-05-01 14:43 ` Willy TARREAU
2003-05-01 15:01 ` Larry McVoy
2003-05-01 15:11 ` Martin J. Bligh
2003-05-01 17:22 ` Balram Adlakha
2003-05-01 17:28 ` Ben Greear
2003-05-01 20:03 ` John Bradford
2003-04-30 23:46 rmoser
2003-05-01 0:21 ` Randy.Dunlap
2003-05-01 0:44 ` rmoser
2003-05-01 2:51 ` Randy.Dunlap
2003-05-01 10:13 ` rmoser
2003-05-01 0:52 ` Larry McVoy
2003-05-01 1:00 ` rmoser
2003-05-01 17:28 ` James H. Cloos Jr.
2003-05-01 4:10 ` Martin J. Bligh
2003-05-01 6:14 ` Ed Sweetman
2003-05-01 6:14 ` Peter Riocreux
2003-05-02 0:09 ` Randy.Dunlap
2003-05-02 0:41 ` rmoser
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=200305011202_MC3-1-36E2-1D26@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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
all inboxes | Powered by JetHome®