All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] libcrypt is old..
Date: Sat, 27 Mar 2010 09:22:41 +0100	[thread overview]
Message-ID: <20100327092241.572378c0@surf> (raw)
In-Reply-To: <7F469B39FAA5453E93B9FA8C4FB29674@apexjs>

On Sat, 27 Mar 2010 01:48:50 +0100
"Sagaert Johan" <sagaert.johan@skynet.be> wrote:

> Why not bumping libcrypt to 1.4.5 (the current one 1.2.4 is from 2005..)
>  
> Change the version,and get rid of the 2 patches.

Good idea. Could you provide a patch ?

Thanks!

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

  reply	other threads:[~2010-03-27  8:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-27  0:48 [Buildroot] libcrypt is old Sagaert Johan
2010-03-27  8:22 ` Thomas Petazzoni [this message]
2010-03-27 15:11   ` [Buildroot] [PATCH] libgcrypt: bump to 1.4.5 llandwerlin at gmail.com
2010-03-29 11:43     ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2010-03-27 13:36 [Buildroot] libcrypt is old Sagaert Johan
2010-03-29 11:45 ` Peter Korsgaard

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=20100327092241.572378c0@surf \
    --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 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.