Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/gdb: add optional support for xz
Date: Tue, 16 Feb 2016 23:19:47 +0100	[thread overview]
Message-ID: <87vb5omh6k.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <n0nsocxmrn.ln2@ID-313208.user.individual.net> (Bernd Kuhls's message of "Wed, 10 Feb 2016 22:34:47 +0100")

>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:

 > Am Wed, 10 Feb 2016 22:14:42 +0100 schrieb Arnout Vandecappelle:
 >> This should probably go in to 2016.02.

 > Hi @all,

 > in the coming days I will post 60-80 patches like this one for a variety 
 > of packages. Currently I only have a list of packages with missing 
 > dependencies, I have yet to prepare the patches for them. Because I 
 > consider them as bugfixes I sent the first patches based on git HEAD, 
 > shall I continue to do so?

Yes, please.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2016-02-16 22:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 20:59 [Buildroot] [PATCH 1/1] package/gdb: add optional support for xz Bernd Kuhls
2016-02-10 20:59 ` [Buildroot] [PATCH 1/1] package/libarchive: add optional support for bzip2 Bernd Kuhls
2016-02-10 21:19   ` Arnout Vandecappelle
2016-02-16 22:15     ` Thomas Petazzoni
2016-02-20 13:49     ` Bernd Kuhls
2016-02-20 23:45       ` Arnout Vandecappelle
2016-02-10 20:59 ` [Buildroot] [PATCH 1/1] package/tiff: add optional support for xz Bernd Kuhls
2016-02-16 22:16   ` Thomas Petazzoni
2016-02-10 21:14 ` [Buildroot] [PATCH 1/1] package/gdb: " Arnout Vandecappelle
2016-02-10 21:34   ` Bernd Kuhls
2016-02-16 22:19     ` Peter Korsgaard [this message]
2016-02-10 21:23 ` Arnout Vandecappelle
2016-02-10 23:04   ` Thomas Petazzoni
2016-02-16 22:14 ` Thomas Petazzoni

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=87vb5omh6k.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