From: Nix <nix@esperi.org.uk>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Linda Walsh <lkml@tlinx.org>
Subject: Re: Makefile targets: tar & rpm pkgs, while using O=<dir> as non-root
Date: Wed, 21 Dec 2005 11:22:03 +0000 [thread overview]
Message-ID: <87hd92n19g.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <20051221081843.GL27946@ftp.linux.org.uk> (Al Viro's message of "Wed, 21 Dec 2005 08:18:43 +0000")
On Wed, 21 Dec 2005, Al Viro stated:
> On Wed, Dec 21, 2005 at 07:49:20AM +0000, Nix wrote:
>> Well, personally I handle patch-application in cp -al'ed trees by doing
>> cp -al via a script, and repatching all currently hardlinked trees
>> (obviously if they are very divergent some patches will fail and I'll
>> have to fix them up by hand).
>
> ... then you edit a file to fix a typo, and have a _nice_ day next Friday
> when you notice that stuff got out of sync.
Your text editor is insufficiently flexible. Mine can snap hardlinks
automatically when st_nlink > 1. :)
(But let's avoid editor wars. I'm sure there's a magic way vim can be
coerced into doing things properly.)
What we really need is an FS that does behind-the-scenes block CoW
and/or block merging anyway; then we could just cp -a the damn tree
and keep the space savings.
>> (And if you're using this to maintain development branches, then you
>> have resync and conflict-management problems *anyway*, which this makes
>> no worse.)
>
> Yes, but it's easier to deal with when the number of your repositories
> doesn't get multiplied by factor of 20 or so...
Er, I don't have a factor of 20 more repositories than anyone else. (I
don't have the disk space for that!)
--
`I must caution that dipping fingers into molten lead
presents several serious dangers.' --- Jearl Walker
next prev parent reply other threads:[~2005-12-21 11:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 23:27 Makefile targets: tar & rpm pkgs, while using O=<dir> as non-root Linda Walsh
2005-12-19 7:19 ` Jan-Benedict Glaw
2005-12-19 22:12 ` Linda Walsh
2005-12-19 22:30 ` Jan-Benedict Glaw
2005-12-20 1:48 ` Linda Walsh
2005-12-30 6:33 ` patch for "scripts/package/buildtar" to pickup "localversion" on "/boot" file objects Linda A. Walsh
2005-12-30 10:15 ` Erik Mouw
2005-12-30 20:23 ` Linda A. Walsh
2005-12-20 15:41 ` Makefile targets: tar & rpm pkgs, while using O=<dir> as non-root Nix
2005-12-20 15:58 ` Sam Ravnborg
2005-12-20 17:44 ` Nix
2005-12-20 17:37 ` Sam Ravnborg
2005-12-20 20:25 ` Al Viro
2005-12-21 7:49 ` Nix
2005-12-21 8:18 ` Al Viro
2005-12-21 11:22 ` Nix [this message]
2005-12-21 8:56 ` Sean
2005-12-21 8:56 ` Sean
2005-12-20 17:20 ` Ryan Anderson
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=87hd92n19g.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.org \
--cc=sam@ravnborg.org \
--cc=viro@ftp.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.