From: Peter Korsgaard <peter@korsgaard.com>
To: Andrey Nechypurenko <andreynech@gmail.com>
Cc: buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] Confusion about 2022.11 release branch
Date: Wed, 14 Dec 2022 20:17:43 +0100 [thread overview]
Message-ID: <874jtxu754.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAOiXNkA74=14gXbkNwBFLrzonWtkGyQ2GnHuXG76C0z-LbrUBg@mail.gmail.com> (Andrey Nechypurenko's message of "Wed, 14 Dec 2022 20:06:31 +0100")
>>>>> "Andrey" == Andrey Nechypurenko <andreynech@gmail.com> writes:
Hi,
> Thank you Peter for the quick response and explanation!
You're welcome!
>> Anything specific you are missing from the 2022.11 release?
> Not really. I am including Buildroot as a submodule in my git repository. So
> I was wondering what tag or branch I have to check out to get the 2022.11
> release.
The '2022.11' tag.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-12-14 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 18:00 [Buildroot] Confusion about 2022.11 release branch Andrey Nechypurenko
2022-12-14 18:57 ` Peter Korsgaard
2022-12-14 19:06 ` Andrey Nechypurenko
2022-12-14 19:17 ` Peter Korsgaard [this message]
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=874jtxu754.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=andreynech@gmail.com \
--cc=buildroot@buildroot.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