Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 02/10] dash: bump to 0.5.8-2
Date: Fri, 14 Nov 2014 14:49:32 +0100	[thread overview]
Message-ID: <87389lhoyb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20141114144256.7486638c@free-electrons.com> (Thomas Petazzoni's message of "Fri, 14 Nov 2014 14:42:56 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 >> > Peter, this one should probably go in 2014.11.
 >> 
 >> Why? Is it security related? I don't see anything special in the
 >> changelog. In fact, I don't see anything affecting us at all:
 >> 
 >> http://metadata.ftp-master.debian.org/changelogs//main/d/dash/dash_0.5.8-2_changelog

 > I should have said: s/should/could/. I believe it's a minor update, and
 > it's adding hash files, so it's fine for 2014.11. But it's your call :)

Ok. It only updates the .hash, we already have it for -1.

Gustavoz, what is the reason for the bump? According to the changelog
the only difference is in the debian packaging (should we also pass
--disable-lineno?)

-- 
Venlig hilsen,
Peter Korsgaard 

  reply	other threads:[~2014-11-14 13:49 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14 12:44 [Buildroot] [PATCHv2 00/10] systemV init without busybox series Gustavo Zacarias
2014-11-14 12:44 ` [Buildroot] [PATCH 01/10] skeleton/S40network: tweak for debian ifupdown Gustavo Zacarias
2014-11-14 21:33   ` Arnout Vandecappelle
2014-11-14 12:44 ` [Buildroot] [PATCH 02/10] dash: bump to 0.5.8-2 Gustavo Zacarias
2014-11-14 13:15   ` Thomas Petazzoni
2014-11-14 13:39     ` Peter Korsgaard
2014-11-14 13:42       ` Thomas Petazzoni
2014-11-14 13:49         ` Peter Korsgaard [this message]
2014-11-14 13:59           ` Gustavo Zacarias
2014-11-14 14:10             ` Peter Korsgaard
2014-11-14 14:14               ` Gustavo Zacarias
2014-11-14 14:16                 ` Peter Korsgaard
2014-11-14 12:44 ` [Buildroot] [PATCH 03/10] debianutils: new package Gustavo Zacarias
2014-11-14 21:35   ` Arnout Vandecappelle
2014-11-14 12:44 ` [Buildroot] [PATCH 04/10] ifupdown: " Gustavo Zacarias
2014-11-14 21:56   ` Arnout Vandecappelle
2014-11-14 22:25     ` Gustavo Zacarias
2014-11-14 12:44 ` [Buildroot] [PATCH 05/10] start-stop-daemon: " Gustavo Zacarias
2014-11-14 13:34   ` Károly Kasza
2014-11-14 13:42     ` Gustavo Zacarias
2014-11-14 13:49       ` Károly Kasza
2014-11-14 22:09   ` Arnout Vandecappelle
2014-11-14 22:26     ` Gustavo Zacarias
2014-11-14 12:44 ` [Buildroot] [PATCH 06/10] package/sysvinit: drop tty1/2 Gustavo Zacarias
2014-11-14 13:17   ` Thomas Petazzoni
2014-11-14 13:36   ` Peter Korsgaard
2014-11-14 12:44 ` [Buildroot] [PATCH 07/10] dhcp: install dhclient to /sbin Gustavo Zacarias
2014-11-14 22:17   ` Arnout Vandecappelle
2014-11-14 22:27     ` Gustavo Zacarias
2014-11-14 12:44 ` [Buildroot] [PATCH 08/10] dhcp: update dhclient-script Gustavo Zacarias
2014-11-14 13:19   ` Thomas Petazzoni
2014-11-14 13:54     ` Gustavo Zacarias
2014-11-14 12:44 ` [Buildroot] [PATCH 09/10] dhcpcd: bump to version 6.6.1 Gustavo Zacarias
2014-11-14 12:44 ` [Buildroot] [PATCH 10/10] dhcpcd: use standard installation Gustavo Zacarias
2014-11-14 22:28   ` Arnout Vandecappelle

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=87389lhoyb.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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