public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: docs@lists.yoctoproject.org,
	"Frédéric Martinsons" <frederic.martinsons@gmail.com>
Subject: Re: [docs] [PATCH 2/3] contributor-guide: add section about why we use mailing lists
Date: Thu, 10 Aug 2023 10:33:27 +0200	[thread overview]
Message-ID: <d5fafe35-8d96-a3ce-5c5b-e31c1165438c@bootlin.com> (raw)
In-Reply-To: <88d3c02eaadc6ce5356608cf93f84dc81471146d.camel@linuxfoundation.org>


On 09.08.23 at 19:57, Richard Purdie wrote:
>>
>> I find the term "point-and-click" a little patronizing,
>> github/gitlab/others web tools
>> are not just point-and-click machine but highly customizable tool
>> aims at smoothen the developer work (in term of tracking, viewing
>> diff, forking) and to provide enhanced user experience.
> I agree we should tweak the wording.


I changed the text to a more neutral "would prefer a web-based GUI".
Done directly in master-next.
Thanks for the review!
Michael.


-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  parent reply	other threads:[~2023-08-10  8:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 14:25 [PATCH 1/3] contributor-guide: add missing links to mailing lists michael.opdenacker
2023-08-09 14:25 ` [PATCH 2/3] contributor-guide: add section about why we use " michael.opdenacker
2023-08-09 15:58   ` [docs] " Frédéric Martinsons
2023-08-09 17:57     ` Richard Purdie
2023-08-09 18:55       ` Frédéric Martinsons
2023-08-10  8:33       ` Michael Opdenacker [this message]
2023-08-10  7:42   ` Daniel Ammann
2023-08-10  8:17     ` Michael Opdenacker
2023-08-09 14:25 ` [PATCH 3/3] contributor-guide: add recipe style guide michael.opdenacker

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=d5fafe35-8d96-a3ce-5c5b-e31c1165438c@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=frederic.martinsons@gmail.com \
    --cc=richard.purdie@linuxfoundation.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