Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] package/jsoncpp: bump version to 1.6.5
Date: Sun, 09 Aug 2015 22:01:49 +0200	[thread overview]
Message-ID: <d6ok9cxek9.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 1439143511.12501.11.camel@embedded.rocks

Am Sun, 09 Aug 2015 20:05:11 +0200 schrieb J?rg Krause:

> I already submitted a patch for jsoncpp version bump and removing the
> snprintf-patch:
> http://patchwork.ozlabs.org/patch/502324/

Hi J?rg,

sorry, I did not notice. I think your patch is better because it takes 
care of the non-c11 toolchains but, as discussed, could you please keep 
the snprintf patch? Therefore I marked my patch as superseded ;)

Regards, Bernd

  reply	other threads:[~2015-08-09 20:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-09 12:28 [Buildroot] [PATCH/next 1/1] package/jsoncpp: bump version to 1.6.5 Bernd Kuhls
2015-08-09 14:54 ` Baruch Siach
2015-08-09 18:05   ` Jörg Krause
2015-08-09 20:01     ` Bernd Kuhls [this message]
2015-08-09 20:13       ` Baruch Siach
2015-08-09 20:35         ` Bernd Kuhls
2015-08-09 20:50           ` Baruch Siach
2015-08-09 20:03     ` Baruch Siach

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=d6ok9cxek9.ln2@ID-313208.user.individual.net \
    --to=bernd.kuhls@t-online.de \
    --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