From: Marcus Osdoba <marcus.osdoba@googlemail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] introducing transmission bittorrent client
Date: Wed, 22 Sep 2010 22:26:15 +0200 [thread overview]
Message-ID: <4C9A6667.90603@googlemail.com> (raw)
In-Reply-To: <AANLkTi=D9f0qz=DsgeX-hwZPwxvSsp-nncS+r0BiqP0y@mail.gmail.com>
Am 21.09.2010 04:00, schrieb Kelvin Cheung:
> Hi Marcus,
>
> I have tried the patch.
> It works fine.
>
> 2010/9/19 Marcus Osdoba <marcus.osdoba@googlemail.com
> <mailto:marcus.osdoba@googlemail.com>>
>
> Am 19.09.2010 10:23, schrieb Marcus Osdoba:
>
> the client has an excellent webinterface
> and seems to be ideal for headless systems,
> the statedirectory is stored in /var/transmission which links
> to tmp,
> the user should provide a writable config direcory
>
> Based on work by: Kelvin Cheung<keguang.zhang@gmail.com
> <mailto:keguang.zhang@gmail.com>>
>
> Signed-off-by: Marcus Osdoba<marcus.osdoba@googlemail.com
> <mailto:marcus.osdoba@googlemail.com>>
> ---
> [...]
>
> Hi Marek and Kelvin,
>
> Are you able to test the new patch for your targets and send some
> (hopefully) positive test results in reply to this patch on the
> mailinglist. Maybe this would fasten the inclusion into upcoming
> release 2010.11.
>
> Regards,
> Marcus
>
>
> --
> Best Regards!
> Kelvin
>
Hi Thomas and Peter,
Is a positive test sufficient for you to have a closer look at it?
Just for the protocol, transmission build breaks with activated
config-cache. If I use it, I have to remove
outbut/build/transmission-2.04 and run make flush;make.
I followed the cache discussion on the mailinglist and I know that this
feature has been marked experimental (which is my preferred solution,
too). But I still use it anyway to speed up the development cycle.
Regards,
Marcus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100922/e9dcdd98/attachment.html>
next prev parent reply other threads:[~2010-09-22 20:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 8:23 [Buildroot] [PATCH] introducing transmission bittorrent client Marcus Osdoba
2010-09-19 9:53 ` Marcus Osdoba
2010-09-21 2:00 ` Kelvin Cheung
2010-09-22 20:26 ` Marcus Osdoba [this message]
2010-09-22 23:06 ` Thomas Petazzoni
2010-09-27 21:46 ` Marcus Osdoba
2010-09-29 8:22 ` Thomas Petazzoni
2010-09-22 23:05 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2010-09-13 18:07 [Buildroot] resend transmission bittorrent client after 1st review by Thomas Marcus Osdoba
2010-09-13 18:07 ` [Buildroot] [PATCH] introducing transmission bittorrent client Marcus Osdoba
2010-09-09 20:28 [Buildroot] transmission better choice over ctorrent according to users voices Marcus Osdoba
2010-09-09 20:28 ` [Buildroot] [PATCH] introducing transmission bittorrent client Marcus Osdoba
2010-09-10 5:07 ` Belisko Marek
2010-09-10 8:10 ` Thomas Petazzoni
2010-09-10 8:15 ` Belisko Marek
2010-09-11 16:32 ` Marcus Osdoba
2010-09-10 6:55 ` 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=4C9A6667.90603@googlemail.com \
--to=marcus.osdoba@googlemail.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