public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: yann.morin@orange.com
To: Florian Larysch <fl@n621.de>
Cc: Romain Naour <romain.naour@smile.fr>, <buildroot@buildroot.org>,
	Christian Stewart <christian@aperture.us>,
	Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH 1/1] package/go: make pre-built compiler provide target support too
Date: Thu, 10 Jul 2025 10:35:36 +0200	[thread overview]
Message-ID: <aG97WEwGhHgMN5p2@yd-6wlzhs3> (raw)
In-Reply-To: <20250709145921.wuzple2z7jrftmjh@n621.de>

Florian, All,

On 2025-07-09 16:59 +0200, Florian Larysch spake thusly:
> On Tue, Jul 08, 2025 at 07:04:22AM +0200, yann.morin@orange.com wrote:
> > So, I've had a go (aha!) at rewriting a commit log as I understood the
> > situation, building upon your initial commit log and trying to account
> > for Romain's comments:
> Thank you! That does seem more straightforward than the original
> message.
[--SNIP--]
> Either way, feel free to commit this with your reworded message. Or
> should I send a v2?

I think you should just resubmit with the updated commit log. Do not
forget to mention, below the '---' line, that is is a v2 that
incorporates an extended commit log, e.g. something like:

    Signed-off-by: Your NAME <your-email>
    Cc: romain <email>
    Cc: yann <email>
    ---
    Changes v1 -> v2:
    - rewrite commit log as suggested by Romain and Yann.

that way, it is easier for a future reviewer to follow what's going on.

Regards,
Yann E. MORIN.

-- 
                                        ____________
.-----------------.--------------------:       _    :------------------.
|  Yann E. MORIN  | Real-Time Embedded |    __/ )   | /"\ ASCII RIBBON |
|                 | Software  Designer |  _/ - /'   | \ / CAMPAIGN     |
| +33 638.411.245 '--------------------: (_    `--, |  X  AGAINST      |
| yann.morin (at) orange.com           |_="    ,--' | / \ HTML MAIL    |
'--------------------------------------:______/_____:------------------'

____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-07-10  8:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 16:21 [Buildroot] [PATCH 1/1] package/go: make pre-built compiler provide target support too Florian Larysch
2025-07-06 16:40 ` Romain Naour via buildroot
2025-07-06 17:13   ` Florian Larysch
2025-07-06 19:59     ` Romain Naour via buildroot
2025-07-07 15:43       ` Florian Larysch
2025-07-08  5:04         ` yann.morin
2025-07-09 14:59           ` Florian Larysch
2025-07-10  8:35             ` yann.morin [this message]
2025-07-14 14:52 ` [Buildroot] [PATCH v2 " Florian Larysch
2025-07-28 14:12   ` Florian Larysch
2025-07-29 11:53   ` yann.morin
2025-08-09 17:27     ` Romain Naour via buildroot
2025-08-14 20:31   ` Thomas Perale via buildroot

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=aG97WEwGhHgMN5p2@yd-6wlzhs3 \
    --to=yann.morin@orange.com \
    --cc=buildroot@buildroot.org \
    --cc=christian@aperture.us \
    --cc=fl@n621.de \
    --cc=romain.naour@smile.fr \
    --cc=thomas.perale@mind.be \
    /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