public inbox for bitbake-devel@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>, antonin.godard@bootlin.com
Cc: quentin.schulz@cherry.de, bitbake-devel@lists.openembedded.org,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	docs@lists.yoctoproject.org
Subject: Re: [bitbake-devel] [docs] [PATCH 1/2] bitbake-setup: rename "abort" rebase conflict stragegy to "halt"
Date: Fri, 03 Apr 2026 11:16:20 +0100	[thread overview]
Message-ID: <ea91cc2bf0fcaeee1a152e62f0ebfd367b58b2fa.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8=z7U5jpCN+NaAmTspYduH=pcMohMcbnqGp8mQvmHoiA@mail.gmail.com>

On Fri, 2026-04-03 at 12:04 +0200, Alexander Kanavin wrote:
> The trouble with ‘reset’ is that it means resetting the whole system
> to its initial state. ‘Abort’ is about a stopping a particular
> operation such that the system is returned to the state before the
> operation started.
> 
> I have no idea how INI has utterly failed to catch these nuances in
> its rationale you linked, and is even accusing the term of ‘lacking
> technical clarity’, but it certainly doesn’t help the cause.

"reset" also struggles as "git reset" means something quite different.

"attempt" is probably the closest other option we have since that
describes what it does rather than the way it recovers, the recovery is
then just implied.

I am torn on this, I recognise the concern around the word, equally,
the word does have two meanings and we do clearly fit one of the cases,
as Alex mentions, we are inheriting the issue from git too. I fear any
change we make here will hurt usability.

Cheers,

Richard






  reply	other threads:[~2026-04-03 10:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31  8:14 [PATCH 0/2] bitbake-setup docs fixes Antonin Godard
2026-03-31  8:14 ` [PATCH 1/2] bitbake-setup: rename "abort" rebase conflict stragegy to "halt" Antonin Godard
2026-03-31  9:00   ` [docs] " Quentin Schulz
2026-03-31 10:43     ` Richard Purdie
2026-03-31 11:36       ` [bitbake-devel] " Alexander Kanavin
2026-04-03  8:07         ` Antonin Godard
2026-04-03 10:04           ` Alexander Kanavin
2026-04-03 10:16             ` Richard Purdie [this message]
2026-03-31  8:14 ` [PATCH 2/2] doc/bitbake-user-manual-environment-setup.rst: replace shell blocks by console Antonin Godard

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=ea91cc2bf0fcaeee1a152e62f0ebfd367b58b2fa.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=antonin.godard@bootlin.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@cherry.de \
    --cc=thomas.petazzoni@bootlin.com \
    /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