mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: 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 06:50:13 +0300	[thread overview]
Message-ID: <20170705065013.ef8a4bdf81cd717cef33f2fb@gmail.com> (raw)
In-Reply-To: <20170630115201.hyeqwm2xxxakwbu7@pengutronix.de>

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.

-- 
Best regards,
  Antony Pavlov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2017-07-05  3:40 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 ` Antony Pavlov [this message]
2017-07-05 10:30   ` v2017.07.0 Ian Abbott

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=20170705065013.ef8a4bdf81cd717cef33f2fb@gmail.com \
    --to=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