public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Separate obj/src dir
Date: Wed, 20 Nov 2002 02:06:59 -0500	[thread overview]
Message-ID: <200211200706.gAK76xA10624@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1037774521.18360.linux-kernel2news@redhat.com>

> On Tue, Nov 19, 2002 at 02:51:54PM -0600, Brian Jackson wrote:
>> Sam Ravnborg writes:=20
>> the build tree, and have the build use the copy in the build tree. Exampl=
> e:=20
>> you want to test a one liner in drivers/scsi/sd.c, you could just copy sd=
> .c=20
>> into the build tree, and make the change and test it out. That could be a=
>=20
>> huge space savings. That would help out those of us that are stuck with=
>=20
>> tiny hard drives in our laptops :)=20
>>=20

> For that you probably want to use the hardlinked trees approach.
> Just do a cp -al linux-2.5 scratch; then change your file and build
> from the copy.
> 
> Simon

One word of caution to vi users: you WILL forget to unlink one day.
So, to protect me from myself, every time I untar a Linus' tree,
I immediately do:
 find linux-2.5.foo -type f | xargs chmod a-w
Then, the attached script reduces the typing. Run "deal dir/file.c"
before editing as if it was "bk edit dir/file.c".
Once you are done I always do:
 diff -urN -X dontdiff linux-2.5.48 linux-2.5.48-sparc > x.diff
This is a blazingly fast with hardlinked tree (cp -al).

-- Pete

#!/bin/sh
# This script dealiases a hardlinked file for editing.

set -e

if [ $# != 1 ]; then
  echo "Usage: deal file" >&2
  exit 1
fi

f=$1

mv $f $f~
cp $f~ $f
chmod u+w $f

  parent reply	other threads:[~2002-11-20  6:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19 20:11 [RFC/CFT] Separate obj/src dir Sam Ravnborg
2002-11-19 20:22 ` Richard B. Johnson
2002-11-19 20:29   ` Sam Ravnborg
2002-11-19 20:46     ` Richard B. Johnson
2002-11-19 20:50       ` Kai Germaschewski
2002-11-19 20:54       ` Sam Ravnborg
2002-11-19 21:37         ` David Woodhouse
2002-11-20  4:04           ` Miles Bader
2002-11-19 21:55         ` Brad Hards
2002-11-19 21:01       ` Daniel Jacobowitz
2002-11-19 21:19         ` Geert Uytterhoeven
2002-11-21 16:54       ` Henning P. Schmiedehausen
2002-11-19 20:31   ` Larry McVoy
2002-11-19 20:43     ` Sam Ravnborg
2002-11-19 20:48     ` Kai Germaschewski
2002-11-19 21:57       ` Sam Ravnborg
2002-11-21 16:53   ` Henning P. Schmiedehausen
2002-11-19 20:51 ` Brian Jackson
2002-11-19 22:05   ` Sam Ravnborg
2002-11-20  6:37   ` Simon Fowler
     [not found]   ` <mailman.1037774521.18360.linux-kernel2news@redhat.com>
2002-11-20  7:06     ` Pete Zaitcev [this message]
2002-11-20 13:10 ` [RFC/CFT] " Alex Riesen
2002-11-20 13:14   ` Alex Riesen

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=200211200706.gAK76xA10624@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=linux-kernel@vger.kernel.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