Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/gettext-tiny: bump version for having msgmerge working
Date: Fri, 25 Oct 2019 23:27:29 +0200	[thread overview]
Message-ID: <20191025232729.75e605bf@windsurf.home> (raw)
In-Reply-To: <20190414095152.18557-1-giulio.benetti@micronovasrl.com>

On Sun, 14 Apr 2019 11:51:52 +0200
Giulio Benetti <giulio.benetti@micronovasrl.com> wrote:

> On current version msgmerge doesn't work properly. It exits giving:
> fopen: No such file or directory
> The problem has been signalled:
> https://github.com/sabotage-linux/gettext-tiny/issues/42
> and fixed with this commit:
> https://github.com/sabotage-linux/gettext-tiny/commit/a597aaebd15ef73a65d67f0d6f746ca7ca812d51
> 
> Bump version to latest commit.
> 
> Fixes:
> http://autobuild.buildroot.net/results/92a/92a43f5dfe4a6df7ab5de7defe078fac58c99d75/
> 
> Signed-off-by: Giulio Benetti <giulio.benetti@micronovasrl.com>
> ---
> Changes:
> V1->V2: improved commit log

Applied to master after tweaking the commit log, especially the fact
that it isn't a fix for the problem seen as we want to fix it
differently.

Thanks!

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

      reply	other threads:[~2019-10-25 21:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 17:46 [Buildroot] [PATCH] package/gettext-tiny: bump version for having msgmerge working Giulio Benetti
2019-04-10 11:37 ` Thomas Petazzoni
2019-04-10 12:38   ` Giulio Benetti
2019-04-11 22:19     ` Vadim Kochan
2019-04-12  8:32       ` Giulio Benetti
2019-04-14  9:51         ` [Buildroot] [PATCH v2] " Giulio Benetti
2019-10-25 21:27           ` Thomas Petazzoni [this message]

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=20191025232729.75e605bf@windsurf.home \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox