From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Matt Mackall <mpm@selenic.com>, David Chinner <dgc@sgi.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com, michal.k.k.piotrowski@gmail.com
Subject: Re: 2.6.21-git10/11: files getting truncated on xfs? or maybe an nlink problem?
Date: Mon, 14 May 2007 13:27:43 -0700 [thread overview]
Message-ID: <4648C63F.7020800@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0705142215130.9570@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
> On May 12 2007 07:46, Matt Mackall wrote:
>
>>> You should not assume alphabetical order. Filesystems may be free to
>>> reorder things and return them (1) randomly like in a hash (2) by
>>> creation time during readdir().
>>>
>> There is no assumption. Mercurial explicitly visits files in
>> alphabetical order for the above commands.
>>
>
> But who says that
>
> for i in {a..z}; do ## {..} is a bash3 extension
> touch $i;
> done;
>
> actually makes readdir() return them in the same order?
Nobody. But doing a readdir, sorting the results and visiting the files
in that order does mean you'll visit them in alphabetical order. Hence
"explicitly visits".
J
next prev parent reply other threads:[~2007-05-14 20:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 21:09 2.6.21-git10/11: files getting truncated on xfs? or maybe an nlink problem? Jeremy Fitzhardinge
2007-05-09 21:55 ` Matt Mackall
2007-05-09 22:17 ` Jeremy Fitzhardinge
2007-05-09 22:44 ` Matt Mackall
2007-05-09 22:50 ` Jeremy Fitzhardinge
2007-05-09 23:16 ` David Chinner
2007-05-09 23:30 ` Jeremy Fitzhardinge
2007-05-10 0:01 ` David Chinner
2007-05-10 0:04 ` Jeremy Fitzhardinge
2007-05-10 0:49 ` David Chinner
2007-05-10 0:54 ` Jeremy Fitzhardinge
2007-05-10 1:26 ` David Chinner
[not found] ` <46433049.4020003@goop.org>
2007-05-10 15:38 ` Matt Mackall
2007-05-12 11:21 ` Jan Engelhardt
2007-05-12 12:46 ` Matt Mackall
2007-05-14 20:16 ` Jan Engelhardt
2007-05-14 20:27 ` Jeremy Fitzhardinge [this message]
2007-05-10 21:13 ` David Chinner
2007-05-10 21:23 ` Matt Mackall
2007-05-10 21:32 ` Jeremy Fitzhardinge
2007-05-10 21:49 ` Jeremy Fitzhardinge
2007-05-10 21:41 ` Chuck Ebbert
2007-05-10 21:46 ` Jeremy Fitzhardinge
2007-05-10 21:51 ` Chuck Ebbert
2007-05-10 21:54 ` Jeremy Fitzhardinge
2007-05-10 22:58 ` David Chinner
2007-05-10 23:07 ` Jeremy Fitzhardinge
2007-05-10 23:27 ` David Chinner
2007-05-10 23:49 ` Jeremy Fitzhardinge
2007-05-11 0:32 ` David Chinner
2007-05-11 14:48 ` Jeremy Fitzhardinge
2007-05-12 7:56 ` David Chinner
2007-05-12 11:23 ` Jan Engelhardt
2007-05-12 13:51 ` David Chinner
2007-05-12 14:56 ` Jeremy Fitzhardinge
2007-05-15 0:14 ` David Chinner
2007-05-15 19:24 ` Jeremy Fitzhardinge
2007-05-10 23:07 ` David Chinner
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=4648C63F.7020800@goop.org \
--to=jeremy@goop.org \
--cc=dgc@sgi.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mpm@selenic.com \
--cc=xfs@oss.sgi.com \
/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