From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is it possible to protect *INDIVIDUAL FILES* against etc-update?
Date: Tue, 17 Oct 2006 15:16:01 +0200 [thread overview]
Message-ID: <200610171516.02085.bo.andresen@zlin.dk> (raw)
In-Reply-To: <20061015132757.283f8283@krikkit.digimed.co.uk>
[-- Attachment #1: Type: text/plain, Size: 489 bytes --]
On Sunday 15 October 2006 14:27, Neil Bothwick wrote:
> As I've mentioned several times before, there was a patch to
> dispatch-conf to do just this. You added the files you didn't want
> touching, ever, to a line in the config file. Unfortunately, the patch
> hasn't been updated for a couple of years and stopped working a while
> ago. Why not re-open the bug at
> http://bugs.gentoo.org/show_bug.cgi?id=68618
https://bugs.gentoo.org/show_bug.cgi?id=151685
--
Bo Andresen
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-17 13:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 16:00 [gentoo-user] where to put mknod & chmod maxim wexler
2006-10-11 16:24 ` Alan McKinnon
2006-10-12 14:44 ` maxim wexler
2006-10-12 17:10 ` Alan McKinnon
2006-10-13 15:22 ` maxim wexler
2006-10-13 15:33 ` Neil Bothwick
2006-10-15 4:40 ` [gentoo-user] Is it possible to protect *INDIVIDUAL FILES* against etc-update? Walter Dnes
2006-10-15 7:06 ` Bo Ørsted Andresen
2006-10-16 21:57 ` Walter Dnes
2006-10-17 0:47 ` Richard Fish
2006-10-18 4:09 ` Walter Dnes
2006-10-17 13:11 ` Neil Bothwick
2006-10-15 12:27 ` Neil Bothwick
2006-10-17 13:16 ` Bo Ørsted Andresen [this message]
2006-10-17 14:28 ` Neil Bothwick
2006-10-13 23:51 ` [gentoo-user] where to put mknod & chmod Drew
2006-10-11 18:09 ` Neil Bothwick
2006-10-11 21:31 ` [gentoo-user] where to put mknod & chmo Richard Fish
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=200610171516.02085.bo.andresen@zlin.dk \
--to=bo.andresen@zlin.dk \
--cc=gentoo-user@lists.gentoo.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