Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/raspberrypi: use the branch name instead of the sha1 for the linux kernel
Date: Fri, 2 May 2014 15:12:05 +0200	[thread overview]
Message-ID: <20140502131205.GC3503@free.fr> (raw)
In-Reply-To: <874n18pbrv.fsf@dell.be.48ers.dk>

Peter, All,

On 2014-05-02 15:09 +0200, Peter Korsgaard spake thusly:
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> 
>  > From: "Yann E. MORIN" <yann.morin.1998@free.fr>
>  > Previously, when we were using the rpi-3.10.y branch, we coiuld use a sha1 to
>  > refer to a specific changeset, and that would work and give reproducible
>  > builds, thanks to upstream merging linux-stable into their branch.
> 
>  > Now they have declared rpi-3.12.y the new stable branch, and deprecated the
>  > rpi-3.10.y branch.
> 
>  > Unfortunately, they are now rebasing the rpi-3.12.y branch instead of merging
>  > linux-stable as they used to do. This means we can no longer use a sha1 as the
>  > tree will change as soon as upstream rebases onto a new linux-stable.
> 
>  > There are two possibilities here:
>  >   - revert back to using a rpi-3.10.y cset
>  >   - use the rpi-3.12.y branch name
> 
>  > This patch goes with the second option, since rpi-3.10.y is no longer maitained,
>  > and we prefer to use a stable branch, at the cost of reproducible builds.
> 
> Hmm, but that means that the builds are not reproducable :/

Indeed, that's a drawback.

> Can't we convince them to create a new branch whenever they rebase or
> something like that?

Already done:
    https://github.com/raspberrypi/linux/issues/584

I forgot to add this in my commit log. Can you do that before you apply,
please, or do you want me to re-submit?

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-05-02 13:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 12:45 [Buildroot] [PATCH] configs/raspberrypi: use the branch name instead of the sha1 for the linux kernel Yann E. MORIN
2014-05-02 13:09 ` Peter Korsgaard
2014-05-02 13:12   ` Yann E. MORIN [this message]
2014-05-02 19:18 ` 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=20140502131205.GC3503@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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