From: Wol <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc
Date: Sat, 15 Jun 2024 18:14:12 +0100 [thread overview]
Message-ID: <1d44a015-cbaa-4447-bed9-df7ebbcfcce3@youngman.org.uk> (raw)
In-Reply-To: <ZmyATIJTWK7KFybD@ACM>
On 14/06/2024 18:39, Alan Mackenzie wrote:
>> Does etc-update or dispatch-conf not give you the option to selectively
>> update and/or to diff the file?
> In theory, yes. In practice, dispatch-conf just offers a single
> ~130-line long hunk, which is useless for distinguishing wanted pieces of
> code from old superseded code. As I say, what's missing is the old
> repository version, which would allow a diff3.
etc-update certainly, and I would be surprised if dispatch-conf didn't,
does offer you a diff.
The (faulty) assumption here is that the user actually knows how to make
use of a diff!
Certainly true for me, and quite likely for a sizeable minority, I
predate both Linux and Windows by quite a large margin, and have never
been part of the Unix eco-system. I use linux because it's better than
Windows, I use gentoo because I want to learn, but I'm not comfortable
with pretty much the entire development ecosystem including things like
diff.
I so rarely use diff, that I find it simplest to run a diff (which tells
me *what* has changed, then I open both old and new in kate, and
manually investigate. It may be more work than using diff properly, but
once I factor in the cost of working out how to use diff it's not worth
it. It's doubly not worth it because I'll have forgotten all that hard
work next time I need it!
Cheers,
Wol
next prev parent reply other threads:[~2024-06-15 17:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <IPhvk-2UIJ-3@gated-at.bofh.it>
2024-06-14 16:19 ` [gentoo-user] Difficulty with updating /etc/basb/bashrc Mike Civil
2024-06-14 17:39 ` Alan Mackenzie
2024-06-14 18:08 ` Waldo Lemmer
2024-06-15 17:14 ` Wol [this message]
2024-06-14 15:53 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-14 18:25 ` 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 20:10 ` Alan Mackenzie
2024-06-17 7:25 ` Wols Lists
2024-06-15 16:39 ` 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=1d44a015-cbaa-4447-bed9-df7ebbcfcce3@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