From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: "Jan Čermák" <sairon@sairon.cz>
Cc: Bernd Kuhls <bernd@kuhls.net>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/linux-firmware: bump version to 20231211
Date: Fri, 19 Jan 2024 21:44:01 +0100 [thread overview]
Message-ID: <ZarfESFB_voB0vC4@landeda> (raw)
In-Reply-To: <8cd703c2-6256-4993-a6c8-aba7a824676d@sairon.cz>
Jan, All,
On 2024-01-17 12:15 +0100, Jan Čermák spake thusly:
> > > Updated WHENCE hash due to various commits:
> > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/WHENCE
> >
> > If the file changed, that is because there were changes upstream, so
> > stating there are "various commits" that changed the file is not very
> > helpful.
> It's a bit vague formulation indeed, however it's accompanied with the link
> to the list of changes in the upstream git tree. Unfortunately cgit UI
> doesn't have a way to specify commit range to limit the list of commits.
> Anyway, I simply followed the example of previous updates of linux-firmware,
> where a similar wording was used:
Right, and that's nice that you looked at previous entries, thanks! :-)
Improving the commit logs is also a long-lasting goal and effort of
mine, one commit at a time! ;-)
Thank you for your contributions!
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-01-19 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 18:33 [Buildroot] [PATCH 1/1] package/linux-firmware: bump version to 20231211 Jan Čermák
2024-01-14 9:06 ` Yann E. MORIN
2024-01-17 11:15 ` Jan Čermák
2024-01-19 20:44 ` Yann E. MORIN [this message]
[not found] <20240109183354.361126-1-sairon__40282.8532781982$1704825264$gmane$org@sairon.cz>
2024-01-13 21:40 ` Bernd Kuhls
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=ZarfESFB_voB0vC4@landeda \
--to=yann.morin.1998@free.fr \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=sairon@sairon.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.