Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] raspberrypi2: kernel version does no more exist
Date: Wed, 8 Apr 2015 23:20:38 +0200	[thread overview]
Message-ID: <20150408232038.4942770f@free-electrons.com> (raw)
In-Reply-To: <1428480480-6422-1-git-send-email-jezz@sysmic.org>

Dear J?r?me Pouiller,

On Wed,  8 Apr 2015 10:08:00 +0200, J?r?me Pouiller wrote:
> It looks like version 2c4959b of Raspberry kernel does no more exist:
> 
> $ git clone https://github.com/raspberrypi/linux.git
> [...]
> $ cd linux
> $ git co 23c76b7f608e51258c6fca02aebeb5d588583149
> fatal: reference is not a tree: 23c76b7f608e51258c6fca02aebeb5d588583149
> 
> Replace it by lastest version of 3.19 branch
> 
> Signed-off-by: J?r?me Pouiller <jezz@sysmic.org>

Yeah, the RPi people are annoying, they constantly rebase their
branches so there's no way to have a stable commit. Yann posted an
issue to their github: https://github.com/raspberrypi/linux/issues/915.
Maybe we need to look into what they propose, apparently they have some
stable branches.

I've nonetheless applied your commit, after tweaking the commit log.

(Hint: "does no more exist" isn't proper English as far as I know, you
should say "does not exist anymore" I believe. Though I'm not a native
English speaker, so I might be wrong.)

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2015-04-08 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08  8:08 [Buildroot] [PATCH] raspberrypi2: kernel version does no more exist Jérôme Pouiller
2015-04-08  8:13 ` Jérôme Pouiller
2015-04-08 21:20 ` Thomas Petazzoni [this message]
2015-04-10 20:09   ` Arnout Vandecappelle
2015-04-10 20:21     ` Thomas Petazzoni
2015-04-28 13:13       ` Frank Hunleth

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=20150408232038.4942770f@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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