From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V2] openocd: fetch package from git repository and update version
Date: Sun, 26 Feb 2012 05:37:06 +0100 [thread overview]
Message-ID: <20120226043705.GD10670@game.jcrosoft.org> (raw)
In-Reply-To: <CAAAP30E8ijhxYh05evremPG9fpkyySo8fjJv18Wc4J2eKuf8rw@mail.gmail.com>
On 00:06 Sun 26 Feb , Alexandre Pereira da Silva wrote:
> >> again NACK
> >>
> >> DO NOT USE GIT in the release
> >
> > ?Instead of just shouting at Alexandre, perhaps you can explain why it's
> > a bad idea to use the git version for openocd...
> >
> > ?Alexandre, why do you need a more recent version than the official
> > release?
>
> The openocd release is 6 months old and they made many improvements
> since then. And I don't see any plans for them to release a new
> version any time soon.
I will release a new version of openocd in time, today the current version is
not stable enough
>
> Openocd git head is usually more stable than their latest released
> version. Specially if the support for the target you are using is new.
> I have had issues connecting one of my cortex-m3 targets with openocd
> 0.5.0.
>
> This is a special package like u-boot and the kernel because in many
> occasions you have to tweak the package to suit your own hardware.
The NACK stand
You can do it for your local but for mainline no, barebox/ u-boot, linux are
based on release
>
> Other option would be to use 0.5.0 version from git, so people who run
> into this kind of issue, can override the version more easily.
NACK
git is very slow to download it's NOT an option at all for default version
>
> Another comment on this issue is about git submodule fetching. Do you
> think that could be useful to other packages? If so, I can prepare a
> new patch to fetch all submodules, if any.
this is yes
Best Regards,
J.
next prev parent reply other threads:[~2012-02-26 4:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 18:19 [Buildroot] [PATCH] openocd: fetch package from git repository and update version Alexandre Pereira da Silva
2012-02-24 19:01 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-24 21:31 ` [Buildroot] [PATCH V2] " Alexandre Pereira da Silva
2012-02-25 3:33 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-25 15:31 ` Arnout Vandecappelle
2012-02-26 3:06 ` Alexandre Pereira da Silva
2012-02-26 4:37 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2012-02-28 20:46 ` Arnout Vandecappelle
2012-02-26 4:39 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-26 4:40 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-28 13:34 ` Thomas Petazzoni
2012-02-28 20:44 ` Peter Korsgaard
2012-02-29 14:42 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-29 17:20 ` Alexandre Pereira da Silva
2012-03-05 10:54 ` Thomas Petazzoni
2012-02-29 18:15 ` 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=20120226043705.GD10670@game.jcrosoft.org \
--to=plagnioj@jcrosoft.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 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.