From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libosip2 : bump version.
Date: Mon, 12 Dec 2011 16:27:22 +0100 [thread overview]
Message-ID: <20111212162722.14634b32@skate> (raw)
In-Reply-To: <87liqhu8tr.fsf@macbook.be.48ers.dk>
Le Mon, 12 Dec 2011 16:08:00 +0100,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> Either use the real upstream or change to a stable snapshot.debian.org
> URL.
Generally speaking, I think we should refuse to use URLs on
ftp.debian.org. Those are *always* changing all the time, and have
already broken the build for numerous packages. They are also causing
problems to people using old versions of Buildroot.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-12-12 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 14:43 [Buildroot] [PATCH 1/1] libosip2 : bump version Sagaert Johan
2011-12-12 15:08 ` Peter Korsgaard
2011-12-12 15:27 ` Thomas Petazzoni [this message]
2011-12-12 15:44 ` Peter Korsgaard
2011-12-12 21:12 ` [Buildroot] [PATCH 1/1] libosip2 : bump version. download no longer available Sagaert Johan
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=20111212162722.14634b32@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