All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/openocd: bump to version 104a5cb
Date: Sun, 22 Dec 2019 13:50:26 +0100	[thread overview]
Message-ID: <20191222135026.75c9cffa@windsurf> (raw)
In-Reply-To: <20191217232657.6582-1-fhunleth@troodon-software.com>

Hello Frank,

On Tue, 17 Dec 2019 18:26:57 -0500
Frank Hunleth <fhunleth@troodon-software.com> wrote:

> The OpenOCD project hasn't made a release since January 2017. Much work
> has happened since then and now. This bumps the version to the latest
> commit and removes a patch that has been applied upstream.
> 
> Signed-off-by: Frank Hunleth <fhunleth@troodon-software.com>

Overall, it certainly looks good to bump OpenOCD, since indeed the
project is essentially no longer tagging any "official" release.

However, there a few changes that I'd like to see:

 - Sync with Fabrice Fontaine, who posted a patch that drops the
   internal jimctl usage, and instead uses our jimtcl package.

 - Create a separate package for libjaylink, and use it in OpenOCD.

 - Thanks to the above two points, drop the OPENOCD_GITSUBMODULES = YES
   variable.

 - Perhaps use the Git mirror at https://repo.or.cz/w/openocd.git,
   which is accessible over https://, and therefore will work better
   for some users behind corporate firewalls.

Could you rework your submission according to these suggestions?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-12-22 12:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17 23:26 [Buildroot] [PATCH] package/openocd: bump to version 104a5cb Frank Hunleth
2019-12-22 12:50 ` Thomas Petazzoni [this message]
2019-12-22 12:53   ` 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=20191222135026.75c9cffa@windsurf \
    --to=thomas.petazzoni@bootlin.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.