From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Michael Nosthoff <buildroot@heine.tech>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [RFC 2/2] docs/manual/migrating.txt: add "individual packages" section
Date: Tue, 3 Aug 2021 21:47:58 +0200 [thread overview]
Message-ID: <20210803194758.GH27036@scaer> (raw)
In-Reply-To: <68f35ba6-c038-6d46-c4ea-ee0cbc46bceb@heine.tech>
Micheal, All,
On 2021-08-03 20:56 +0200, Michael Nosthoff spake thusly:
> On 03.08.21 17:19, Arnout Vandecappelle wrote:
> >On 03/08/2021 07:48, Yann E. MORIN wrote:
> >>On 2021-08-02 18:22 +0200, Arnout Vandecappelle (Essensium/Mind) spake thusly:
> >>>Add a section to the migrating documentation to explain what changed in
> >>>individual packages and how it may affect your build.
[--SNIP--]
> >>Instead, I would just suggest that people run "git log --oneline" or
> >>"git log -p --stat" on the packages they are interested in.
> > That's good advice as well. Simple "git log" should be sufficient though, if
> >the commit log is OK. "git log --oneline" is definitely not OK, because
> >important changes during a version bump will not appear in the oneline.
> >
> > I'm going to add a bullet point for this and merge it into the first patch.
>
> One thing I want to point out: The releases are tarballs. Should we assume
> the user has the git history available?
People are really still using tarballs in these days? ;-) But OK, you've
got a point.
However, I would still think that people who want to follow a process
when updating are probably already using buildroot a git submodule of
some sorts, so yes, they will have a git tree to look at.
People who use a released tarball are not really looking for a sustained
or long-term vision, and are not planning on upgrading.
So, I think we can state something like:
- look at the CHANGES file, and run 'git log' on the packages of your
interest; if you are not using git, clone the upstream repository
for this.
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@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-08-03 19:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 16:22 [Buildroot] [RFC 1/2] docs/manual/migrating.txt: add section with general migrating tips Arnout Vandecappelle (Essensium/Mind)
2021-08-02 16:22 ` [Buildroot] [RFC 2/2] docs/manual/migrating.txt: add "individual packages" section Arnout Vandecappelle (Essensium/Mind)
2021-08-03 5:48 ` Yann E. MORIN
2021-08-03 15:19 ` Arnout Vandecappelle
2021-08-03 18:56 ` Michael Nosthoff via buildroot
2021-08-03 19:47 ` Yann E. MORIN [this message]
2021-08-03 21:35 ` Thomas Petazzoni
2021-08-02 20:55 ` [Buildroot] [RFC 1/2] docs/manual/migrating.txt: add section with general migrating tips Yann E. MORIN
2021-08-03 15:18 ` Arnout Vandecappelle
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=20210803194758.GH27036@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=buildroot@heine.tech \
--cc=thomas.petazzoni@bootlin.com \
/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.