From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/proftpd
Date: Wed, 18 Jun 2008 11:22:06 +0200 [thread overview]
Message-ID: <20080618092206.GE32192@mx.loc> (raw)
In-Reply-To: <20080618084529.3973AF8007@busybox.net>
On Wed, Jun 18, 2008 at 01:45:28AM -0700, jacmet at uclibc.org wrote:
>Author: jacmet
>Date: 2008-06-18 01:45:23 -0700 (Wed, 18 Jun 2008)
>New Revision: 22407
>
>Log:
>proftp: bump version and fix compilation on 2.6.24+
>
>Based on patch by Thiago A. Corr?\234a.
>
>
>Added:
> trunk/buildroot/package/proftpd/proftpd-1.3.1-bcopy.patch
this sounds like it should work without patching by just configuring
properly. Also these patches are usually named "susv3.*legacy" for
consistency.
> trunk/buildroot/package/proftpd/proftpd-1.3.1-fix-kernel-header-capability-version.patch
That one would make me nervous if i would use proftpd but there
is vsftpd anyway and luckily i don't do neither.
next prev parent reply other threads:[~2008-06-18 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 8:45 [Buildroot] svn commit: trunk/buildroot/package/proftpd jacmet at uclibc.org
2008-06-18 9:22 ` Bernhard Fischer [this message]
2008-06-18 10:18 ` Peter Korsgaard
2008-06-18 13:48 ` Thiago A. Corrêa
2008-06-18 13:56 ` Thiago A. Corrêa
2008-06-18 14:21 ` Peter Korsgaard
2008-06-18 14:39 ` Bernhard Fischer
2008-06-18 14:57 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2008-06-18 14:21 jacmet at uclibc.org
2007-09-26 10:21 ulf at uclibc.org
2007-07-28 15:21 ulf at uclibc.org
2007-07-17 0:22 sjhill at uclibc.org
2007-07-11 13:55 ulf at uclibc.org
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=20080618092206.GE32192@mx.loc \
--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.