From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc
Date: Mon, 17 Jun 2024 08:25:16 +0100 [thread overview]
Message-ID: <1b660463-868d-4a26-9011-2f4dd246a346@youngman.org.uk> (raw)
In-Reply-To: <Zm31TOnZ5yScRn1h@ACM>
On 15/06/2024 21:10, Alan Mackenzie wrote:
>> Why didn't you keep a copy of the old file?
> Because that's one of the itsy-bitsy routine things that ought to be
> automatic, not something that each user should have to think out for
> himself.
Dunno which update tool it is, but istr there is a tool that does
exactly that ...
>
> It turns out I actually had the old file in /etc/config-archive all
> along. It's a shame dispatch-conf and friends don't do an automatic
> 3-way merge. This would make things so much simpler and less stressful.
Until it gets it wrong. Which is exactly why it doesn't. Which is why
git doesn't. Which is why pretty much all tools don't. If they can
figure it out they do, but they don't charge ahead regardless.
Cheers,
Wol
next prev parent reply other threads:[~2024-06-17 7:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 15:53 [gentoo-user] Difficulty with updating /etc/basb/bashrc Alan Mackenzie
2024-06-14 16:22 ` netfab
2024-06-14 17:33 ` Alan Mackenzie
2024-06-14 17:47 ` netfab
2024-06-14 17:52 ` netfab
2024-06-15 19:52 ` Alan Mackenzie
2024-06-15 11:39 ` Peter Humphrey
2024-06-16 14:26 ` [gentoo-user] " Nuno Silva
2024-06-14 18:25 ` [gentoo-user] " Vitaliy Perekhovy
2024-06-14 20:54 ` Jack
2024-06-15 6:38 ` Vitaliy Perekhovy
2024-06-15 22:00 ` Jack
2024-06-15 22:24 ` Peter Humphrey
2024-06-15 19:58 ` Alan Mackenzie
2024-06-14 23:43 ` Paul Colquhoun
2024-06-15 8:51 ` Re[2]: " Stefan Schmiedl
2024-06-15 20:10 ` Alan Mackenzie
2024-06-17 7:25 ` Wols Lists [this message]
2024-06-15 16:39 ` Wol
[not found] <IPhvk-2UIJ-3@gated-at.bofh.it>
2024-06-14 16:19 ` Mike Civil
2024-06-14 17:39 ` Alan Mackenzie
2024-06-14 18:08 ` Waldo Lemmer
2024-06-15 17:14 ` Wol
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=1b660463-868d-4a26-9011-2f4dd246a346@youngman.org.uk \
--to=antlists@youngman.org.uk \
--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