From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot-20070720
Date: Wed, 22 Aug 2007 01:08:18 +0200 [thread overview]
Message-ID: <20070821230818.GS11697@aon.at> (raw)
In-Reply-To: <1187730489.15882.7.camel@86-115-11-152>
On Tue, Aug 21, 2007 at 11:08:09PM +0200, Ulf Samuelsson wrote:
>Since the buildroot ftp site only maintains one month old tarball,
>this package has already disappeared.
>It would be good if that tarball could be downloadable as well
>so that the diff can be computed.
To me this doesn't make any sense at all.
svn co -r'{2007-07-20 00:00}' svn://uclibc.org/trunk/buildroot buildroot
What do you want to achieve with a tarball? Doesn't svn diff work just
fine? And, what's special about that 20070720 snapshot in the first
place?
next prev parent reply other threads:[~2007-08-21 23:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 21:08 [Buildroot] buildroot-20070720 Ulf Samuelsson
2007-08-21 23:08 ` Bernhard Fischer [this message]
2007-08-22 3:47 ` Ulf Samuelsson
2007-08-22 8:08 ` Bernhard Fischer
2007-08-22 12:19 ` Ulf Samuelsson
2007-08-22 12:40 ` Bernhard Fischer
2007-08-22 16:43 ` Ulf Samuelsson
2007-08-22 19:19 ` Bernhard Fischer
2007-08-22 19:22 ` Benjamin Tietz
2007-08-22 4:35 ` Ulf Samuelsson
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=20070821230818.GS11697@aon.at \
--to=rep.dot.nop@gmail.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.