From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: gnu_andrew@member.fsf.org
Cc: Matthias Klose <doko@ubuntu.com>, GCC Java <java@gcc.gnu.org>,
debian-arm@lists.debian.org, debian-alpha@lists.debian.org,
distro-pkg-dev@openjdk.java.net
Subject: Re: icedtea6 build failures on alpha and armel using gcj
Date: Mon, 08 Mar 2010 14:36:00 -0000 [thread overview]
Message-ID: <20100308143630.GM4307@caffeine.csclub.uwaterloo.ca> (raw)
In-Reply-To: <17c6771e1003080444o3991c1bck4ce0b234c684878e@mail.gmail.com>
On Mon, Mar 08, 2010 at 12:44:59PM +0000, Andrew John Hughes wrote:
> Ok, I didn't realise it was a hard linked copy. I'll disable that; we
> don't want the ecj patches affecting the main tree.
Applying a patch to a hardlink copy does not affect other copies.
patch creates a new file (hence breaking the hardlink). At least when
using the patch command in the default way. Maybe it has an option for
working in place on files, but I have never looked for such an option
so I have no idea.
The linux kernel package has been relying on this for years as have many
other packages.
Please don't change it since it won't make any difference other than to
take more diskspace and time to do a build.
--
Len Sorensen
next prev parent reply other threads:[~2010-03-08 14:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 16:49 Matthias Klose
2010-03-01 19:54 ` Andrew John Hughes
2010-03-08 11:46 ` Matthias Klose
2010-03-08 12:35 ` Andrew John Hughes
2010-03-08 12:41 ` Matthias Klose
2010-03-08 12:45 ` Andrew John Hughes
2010-03-08 14:36 ` Lennart Sorensen [this message]
2010-03-08 15:17 ` Andrew John Hughes
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=20100308143630.GM4307@caffeine.csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=debian-alpha@lists.debian.org \
--cc=debian-arm@lists.debian.org \
--cc=distro-pkg-dev@openjdk.java.net \
--cc=doko@ubuntu.com \
--cc=gnu_andrew@member.fsf.org \
--cc=java@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).