From: "Sean" <seanlkml@sympatico.ca>
To: "Nix" <nix@esperi.org.uk>
Cc: "Al Viro" <viro@ftp.linux.org.uk>,
"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 03:56:43 -0500 (EST) [thread overview]
Message-ID: <BAYC1-PASMTP065003A7F9B2D70E84AE57AE310@CEZ.ICE> (raw)
Message-ID: <52666.10.10.10.28.1135155403.squirrel@linux1> (raw)
In-Reply-To: <87psnqnb3z.fsf@amaterasu.srvr.nix>
On Wed, December 21, 2005 2:49 am, Nix said:
> 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).
>
> It works for me well enough to keep hardlinked branches going for in
> some cases years without problems.
Well the O= syntax is much nicer when using Git. You symply checkout the
branch you're interested in and compile it; then switch to another,
compile it, etc... Git makes checking out a brach lightning fast, it's
very slick. Using the O= notation means you only have one branch checked
out at a time and there's no need to have source files linked to a bunch
of different directories.
Cheers,
Sean
next prev parent reply other threads:[~2005-12-21 8:56 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
[not found] ` <52666.10.10.10.28.1135155403.squirrel@linux1>
2005-12-21 8:56 ` Sean [this message]
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=BAYC1-PASMTP065003A7F9B2D70E84AE57AE310@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.org \
--cc=nix@esperi.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox