From: Ian Abbott <abbotti@mev.co.uk>
To: Antony Pavlov <antonynpavlov@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Lucas Stach <l.stach@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>, lst@pengutronix.de
Subject: Re: v2017.07.0
Date: Wed, 5 Jul 2017 11:30:40 +0100 [thread overview]
Message-ID: <ab51e86b-d22a-f29a-4b23-12f3abe26121@mev.co.uk> (raw)
In-Reply-To: <20170705065013.ef8a4bdf81cd717cef33f2fb@gmail.com>
On 05/07/17 04:50, Antony Pavlov wrote:
> On Fri, 30 Jun 2017 13:52:01 +0200
> Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
>> Hi All,
>>
>> I just releaed barebox-2017.07.0. The reason for this early release is
>> that I am away for the next two months. During this time Lucas will take
>> over maintainership and also make the next release.
>>
>> Most notable new feature this time I think is the support for links to
>> directories.
>
> Hi!
>
> It looks like the commit
>
> commit a602bebcf7e42eb8933f224c12cad1c9320e28a1
> Author: Sascha Hauer <s.hauer@pengutronix.de>
> Date: Tue May 9 07:38:48 2017 +0200
>
> fs: Implement links to directories
>
> breaks tftp command: the command can't anymore download file from subdirectory,
> e.g.
>
> barebox:/ tftp antony/zbarebox
> could not open /.tftp_tmp_path/antony/zbarebox: Invalid argument
>
> barebox:/ tftp zbarebox
> [#################################################################]
> barebox:/
>
> Reverting 944bf0e1 ('fixup! fs: Implement links to directories') and
> a602bebc ('fs: Implement links to directories') fixes the problem.
>
I just tried to reproduce it since the patch had caused me other
problems, but I couldn't reproduce it on my custom board:
barebox@Belltech dbPod SoCFPGA Fast:/ version
barebox 2017.07.0 #2 Wed Jul 5 10:46:41 BST 2017
barebox@Belltech dbPod SoCFPGA Fast:/ tftp antony/zbarebox
[#################################################################]
barebox@Belltech dbPod SoCFPGA Fast:/
I don't think it should matter, but for reference, I'm using atftpd as
my TFTP server.
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-07-05 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 11:52 v2017.07.0 Sascha Hauer
2017-07-05 3:50 ` v2017.07.0 Antony Pavlov
2017-07-05 10:30 ` Ian Abbott [this message]
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=ab51e86b-d22a-f29a-4b23-12f3abe26121@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=l.stach@pengutronix.de \
--cc=lst@pengutronix.de \
--cc=s.hauer@pengutronix.de \
/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