All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork cleanup, week #22
Date: Sun, 26 Jun 2016 13:20:52 +0200	[thread overview]
Message-ID: <1466940052.32055.17.camel@embedded.rocks> (raw)
In-Reply-To: <20160615215258.5e9e85a6@free-electrons.com>

On Mi, 2016-06-15 at 21:52 +0200, Thomas Petazzoni wrote:
> Hello,
> 
> On Wed, 1 Jun 2016 23:26:54 +0200, Thomas Petazzoni wrote:
> 
> > If there is no interest shown in a given patch, either by the
> > original
> > contributor or by another Buildroot developer within the two weeks
> > time, I'll mark the patch as "Rejected" due to the lack of
> > interest.
> > I'm sending this e-mail on June 1st, so on June 15th, for the
> > patches
> > that have not seen any discussion or activity, I'll mark them as
> > Rejected.
> 
> We are on June 15th.
> 
> > Here is the list of week #22 :
> > 
> > ?1/ package/libgpg-error: bump to version 1.21
> > ????http://patchwork.ozlabs.org/patch/562100/
> > 
> > ????I don't really have any comments, other than the fact that it
> > is
> > ????super annoying for a package with so many dependencies to start
> > ????having architecture dependencies. Could someone refresh and
> > ????validate this patch?
> 
> I'm keeping this one around, since we really want to bump libgpg-
> error
> at some point.

Sorry for not taking part in the discussion yet! I suggest to put some
effort to find an upstreamable solution. As Yann has noted I did a
proposal to remove the architecture dependency. However, I do not
understand the concern of the maintainer about ABI compliance. There
was no reaction to my last mail whereupon I stopped working on this
issue for now.

Anyone else interested in helping to solve this issue?

Best regards
J?rg Krause

      parent reply	other threads:[~2016-06-26 11:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-01 21:26 [Buildroot] Patchwork cleanup, week #22 Thomas Petazzoni
2016-06-01 21:53 ` Peter Seiderer
2016-06-02  7:17   ` Thomas Petazzoni
2016-06-02 22:46     ` Yann E. MORIN
2016-06-02  7:41 ` Jeroen Roovers
2016-06-02  7:49   ` Thomas Petazzoni
2016-06-02  8:24     ` Jeroen Roovers
2016-06-02 22:38 ` Yann E. MORIN
2016-06-03  9:11   ` Yegor Yefremov
2016-06-03 19:55 ` Carlos Santos
2016-06-08 20:13 ` Thomas Petazzoni
2016-06-09  8:02   ` Romain Izard
2016-06-09  8:09     ` Thomas Petazzoni
2016-06-15 19:52 ` Thomas Petazzoni
2016-06-16 15:11   ` Carlos Santos
2016-06-26 11:20   ` Jörg Krause [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=1466940052.32055.17.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --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.