From: Roy Wright <roy@wright.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] dispatch-conf merge
Date: Wed, 3 Jun 2009 00:34:53 -0500 [thread overview]
Message-ID: <9F0D6078-DBB3-4820-B498-85A7F7B0DD30@wright.org> (raw)
In-Reply-To: <87zlcpc2pl.fsf@newton.gmurray.org.uk>
On Jun 3, 2009, at 12:21 AM, Graham Murray wrote:
> Is there any way to improve the granularity in the merge function of
> dispatch-conf, or make it more intelligent?
>
> The particular situation where it gives me problems is in
> configuration
> files where the value of an option has been manually changed following
> initial installation, then on an upgrade a new option is added close
> to
> the one previously changed. In this situation, dispatch-conf almost
> invariably wants to reset the changed option line back to its default.
> When selecting 'm' to merge changes it will present a left hand side
> with the already existing value (often plus other lines) with the
> right
> hand side with the default lines for both the existing line(s) and the
> new ones.
>
My habit when manually tweaking a config file is to copy the line then
comment
out the original, like:
original:
foo=some default
changed to:
#foo=some default
foo=bar
this seems to help dispatch-conf some.
For really ugly merges, I just skip in dispatch-conf, then merge using
kdiff3.
HTH,
Roy
next prev parent reply other threads:[~2009-06-03 5:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 5:21 [gentoo-user] dispatch-conf merge Graham Murray
2009-06-03 5:34 ` Roy Wright [this message]
2009-06-03 7:30 ` Volker Armin Hemmann
2009-06-03 7:52 ` Neil Bothwick
2009-06-03 15:58 ` Peter Humphrey
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=9F0D6078-DBB3-4820-B498-85A7F7B0DD30@wright.org \
--to=roy@wright.org \
--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