From: "A. Khattri" <ajai@bway.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Proposed option for etc-update
Date: Mon, 29 Aug 2005 01:59:37 -0400 (EDT) [thread overview]
Message-ID: <Pine.BSO.4.58.0508290156490.24511@ida.bway.net> (raw)
In-Reply-To: <200508271857.51640.k.o.schultz@gmx.net>
On Sat, 27 Aug 2005, Kai Ole Schultz wrote:
> Why not use dispatch-conf instead?
Because it has some annoying quirks of its own that made me go back to
etc-update. Etc-update would be perfect if it had the archiving features
added to it. That said, I would rather use it (and be very very careful)
rather than put up with dispatch-conf.
--
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-29 6:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-27 16:44 [gentoo-user] Proposed option for etc-update Joe Menola
2005-08-27 16:57 ` Kai Ole Schultz
2005-08-27 17:16 ` Joe Menola
2005-08-29 5:59 ` A. Khattri [this message]
2005-08-29 11:42 ` Michael W. Holdeman
2005-08-27 17:00 ` Alex Schuster
2005-08-29 22:05 ` Fernando Canizo
2005-08-28 2:46 ` [gentoo-user] " Alvin A ONeal Jr
2005-08-28 10:44 ` Neil Bothwick
2005-08-30 7:26 ` [gentoo-user] " George Garvey
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=Pine.BSO.4.58.0508290156490.24511@ida.bway.net \
--to=ajai@bway.net \
--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