Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] mx53loco: update support
Date: Mon, 20 Oct 2014 12:58:59 +0200	[thread overview]
Message-ID: <87iojfatxo.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20141020103131.438fb440@e6520eb.localdomain> ("Eric Bénard"'s message of "Mon, 20 Oct 2014 10:31:31 +0200")

>>>>> "Eric" == Eric B?nard <eric@eukrea.com> writes:

Hi,

 >> fslc? Do you mean Freescale?
 >> 
 > fscl means "Freescale Community" : 

fslc ;)

 > http://freescale.github.io/
 > https://community.freescale.com/welcome
 > so the suffix -fslc is added to u-boot & linux git trees :
 > https://github.com/Freescale/u-boot-fslc
 > https://github.com/Freescale/linux-fslc

Ok, thanks.


 >> I prefer to keep the section comments, but OK.
 >> 
 > make savedefconfig automagically removed the comments.
 > I you prefer I can manually reintroduce them.

I think it is nicer for consistency, but I can add them as well when
committing.


 >> >  BR2_LINUX_KERNEL=y
 >> >  BR2_LINUX_KERNEL_CUSTOM_GIT=y
 >> >  BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://git.freescale.com/imx/linux-2.6-imx.git"
 >> > -BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_2.6.35_11.09.01"
 >> > +BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="imx_2.6.35_maintain"
 >> 
 >> _VERSION has to uniquely specify a revision, so it must be a tag or a
 >> sha1 - And not a branch.
 >> 
 > then the help is misleading as it says (for
 > BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION and for
 > BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION) :
 > "Revision to use in the typical format used by Git/Mercurial
 > E.G. a sha id, a tag, _branch_ , .. "

Ahh yes, I'll fix that. The problem about using a branch is that the
downloading infrastructure thinks the branch name uniquely identifies
the code, so it will only download it once even if more commits are
pushed to the branch later.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2014-10-20 10:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20  7:38 [Buildroot] [PATCH 1/2] mx53loco: update support Eric Bénard
2014-10-20  7:38 ` [Buildroot] [PATCH 2/2] imx6sabresd/create-boot-sd.sh: allow usage for i.MX53 Eric Bénard
2014-10-20  8:03 ` [Buildroot] [PATCH 1/2] mx53loco: update support Peter Korsgaard
2014-10-20  8:31   ` Eric Bénard
2014-10-20 10:58     ` Peter Korsgaard [this message]
2014-10-20  8:41 ` Thomas Petazzoni

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=87iojfatxo.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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