From: George Anzinger <george@mvista.com>
To: Dan Aloni <karrde@callisto.yi.org>
Cc: Ivan Passos <lists@cyclades.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Patch generation
Date: Fri, 10 Nov 2000 12:13:08 -0800 [thread overview]
Message-ID: <3A0C56D4.99E4F5D@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011102139170.21416-100000@callisto.yi.org>
Dan Aloni wrote:
>
> On Fri, 10 Nov 2000, George Anzinger wrote:
>
> > > 4 kernel trees, one after make dep ; make bzImage, and all taking together
> > > just 193MB, instead of about 400MB... hard links, gotta love'em.
> >
> > Ok, this is cool, but suppose I have the same file linked to all these
> > and want to change it in all the trees, i.e. still have one file. Is
> > there an editor that doesn't unlink. Or maybe cp of the edited file??
> > How would you do this? (I prefer EMACS, which likes to unlink.)
>
> I know mcedit doesn't unlink (but mcedit kinda sucks), I think nedit
> doesn't unlink too.
>
> I prefer an editor that unlinks, since in most cases I don't want to
> modify the source trees that I'm not working on, so diff can do what it's
> supposed to do later.
Oh, I agree, but I am working on several things at once so my
development trees are cascaded, usually with a kgdb patch in all of
them. If I make a change to kgdb, for example, it would be nice to only
have to change it once, so occasionally, I want to do it differently.
George
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-10 20:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 22:46 Patch generation Ivan Passos
2000-11-09 22:56 ` Chmouel Boudjnah
2000-11-09 22:57 ` Infamous Woodchuck
2000-11-09 23:08 ` Dan Aloni
2000-11-10 16:53 ` George Anzinger
2000-11-10 19:46 ` Dan Aloni
2000-11-10 20:13 ` George Anzinger [this message]
2000-11-11 3:56 ` Peter Samuelson
2000-11-11 5:31 ` Chmouel Boudjnah
2000-11-11 7:30 ` Peter Samuelson
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=3A0C56D4.99E4F5D@mvista.com \
--to=george@mvista.com \
--cc=karrde@callisto.yi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@cyclades.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