From: "Benedikt Morbach" <benedikt.morbach@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] 2 dispatch-conf questions
Date: Sun, 30 Mar 2008 19:18:32 +0200 [thread overview]
Message-ID: <6faa67950803301018g75f00186occ69ef6721e110db@mail.gmail.com> (raw)
In-Reply-To: <200803261734.41805.wonko@wonkology.org>
Hi,
On Wed, Mar 26, 2008 at 6:34 PM, Alex Schuster <wonko@wonkology.org> wrote:
> Question 2: I also have replace-unmodified=yes, but I often see files that I
> never even looked at before. What about that?
That's because dispatch-conf saves every file it processes in it's
archive directory.
When checking if you modified a file, it compares it to the one in it's archive.
So you have to look at each file at least once, because when it is
changed the first time, dispatch-conf does not have the old version
Benedikt
--
gentoo-user@lists.gentoo.org mailing list
prev parent reply other threads:[~2008-03-30 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 16:34 [gentoo-user] 2 dispatch-conf questions Alex Schuster
2008-03-30 17:18 ` Benedikt Morbach [this message]
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=6faa67950803301018g75f00186occ69ef6721e110db@mail.gmail.com \
--to=benedikt.morbach@googlemail.com \
--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