From: Peter Korsgaard <peter@korsgaard.com>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: linux-amarula@amarulasolutions.com,
"Yann E . Morin" <yann.morin.1998@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/3] package/bmap-tools: update GitHub URL
Date: Tue, 07 May 2024 23:08:06 +0200 [thread overview]
Message-ID: <87v83ptjnt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CABGWkvrNG00oAH0mL7Qb5BoQ3WpCtbK=ywmJAMNPtJ+msvieHA@mail.gmail.com> (Dario Binacchi's message of "Tue, 7 May 2024 22:10:28 +0200")
>>>>> "Dario" == Dario Binacchi <dario.binacchi@amarulasolutions.com> writes:
Hi,
> Since this patch is the first in a series of 3, where the final patch
> bumps the version to 3.8.0, what are your
> thoughts on the 2024.02.x version?
> Is there anything I need to do?
No, it is fine. I will just skip the patches for 2024.02.x.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-05-07 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 13:05 [Buildroot] [PATCH v2 1/3] package/bmap-tools: update GitHub URL Dario Binacchi
2024-04-14 13:05 ` [Buildroot] [PATCH v2 2/3] package/bmap-tools: rename Kconfig prompt to bmaptool Dario Binacchi
2024-04-14 13:05 ` [Buildroot] [PATCH v2 3/3] package/bmap-tools: bump to version 3.8.0 Dario Binacchi
2024-04-15 16:29 ` Yann E. MORIN
2024-05-07 16:06 ` [Buildroot] [PATCH v2 1/3] package/bmap-tools: update GitHub URL Peter Korsgaard
2024-05-07 18:58 ` Dario Binacchi
2024-05-07 19:39 ` Peter Korsgaard
2024-05-07 20:10 ` Dario Binacchi
2024-05-07 21:08 ` Peter Korsgaard [this message]
2024-05-07 20:09 ` Yann E. MORIN
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=87v83ptjnt.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.