From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001541]: NCFTP don't download
Date: Thu, 18 Oct 2007 16:37:02 -0700 [thread overview]
Message-ID: <4154625e08f3dec89f32fcb6ecc7d343@bugs.uclibc.org> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=1541
======================================================================
Reported By: sushisan
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1541
Category: Architecture Specific
Reproducibility: always
Severity: crash
Priority: normal
Status: assigned
======================================================================
Date Submitted: 10-18-2007 16:37 PDT
Last Modified: 10-18-2007 16:37 PDT
======================================================================
Summary: NCFTP don't download
Description:
ncftp-3.2.0-src.tar.bz2 are not any more in the repo
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
10-18-07 16:37 sushisan New Issue
10-18-07 16:37 sushisan Status new => assigned
10-18-07 16:37 sushisan Assigned To => buildroot
10-18-07 16:37 sushisan File Added: br2-ncftp.patch
======================================================================
next reply other threads:[~2007-10-18 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 23:37 bugs at busybox.net [this message]
2007-10-19 20:42 ` [Buildroot] [buildroot 0001541]: NCFTP don't download Ivan Kuten
2007-10-19 21:34 ` Bernhard Fischer
2007-10-19 22:42 ` Ivan Kuten
2007-10-19 21:42 ` Bernhard Fischer
-- strict thread matches above, loose matches on Subject: below --
2007-10-19 2:40 bugs at busybox.net
2007-10-19 19:55 bugs at busybox.net
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=4154625e08f3dec89f32fcb6ecc7d343@bugs.uclibc.org \
--to=bugs@busybox.net \
--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