Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] libtool : bump to version 2.4.2
Date: Mon, 13 May 2013 17:38:23 +0200	[thread overview]
Message-ID: <20130513173823.7b5b5186@skate> (raw)
In-Reply-To: <1570358723.2368493.1368458982853.JavaMail.root@openwide.fr>

Dear Jeremy Rosen,

On Mon, 13 May 2013 17:29:42 +0200 (CEST), Jeremy Rosen wrote:
> I needed to bump libtool because pulseaudio needed it.
> 
> I built my system (including pulseaudio) and tested it, but I didn't 
> give it further (enough) thought.
> 
> This prbably means that this patch should not go in master but in 
> next... It's probably way too late to bump libtool.

Version bumps are no longer going to master anyway, not even the
pulseaudio version bump. At this point, master is only about bug fixes,
so it's certainly not the time to bump packages!

> I'll do the allyesconfig test and reply with the results when done...

If you want, I can test the patch here on an allyespackageconfig build.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-05-13 15:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13  8:57 [Buildroot] [PATCH 1/2] libtool : bump to version 2.4.2 Jérémy Rosen
2013-05-13  8:57 ` [Buildroot] [PATCH 2/2] pulseaudio : bump to version 3.0 Jérémy Rosen
2013-05-13  9:27 ` [Buildroot] [PATCH 1/2] libtool : bump to version 2.4.2 Thomas Petazzoni
2013-05-13 15:29   ` Jeremy Rosen
2013-05-13 15:38     ` Thomas Petazzoni [this message]
2013-05-13 16:19       ` Jeremy Rosen
  -- strict thread matches above, loose matches on Subject: below --
2013-05-29  7:11 [Buildroot] [PATCH 0/2] Bump pulseaudio and dependencies Jérémy Rosen
2013-05-29  7:11 ` [Buildroot] [PATCH 1/2] libtool : bump to version 2.4.2 Jérémy Rosen
2013-05-07 16:46 Jérémy Rosen

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=20130513173823.7b5b5186@skate \
    --to=thomas.petazzoni@free-electrons.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