You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Stephen Davis <su...@soundgeek.org> on 2006/05/22 17:49:45 UTC
Why do updated files come in "random" order?
When I do an update, the files that come down are not in alphabetical
order but are instead in a seemingly random order. Directories are
also returned in non-alphabetical order.
A www
A www/project_window.png
A www/index.html
A www/OldReleaseNotes.html
Updated to revision 500.
This is obviously not a critical issue but it is visually
disconcerting. I'm just wondering why svn works this way. When you
browse the repository in your web browser it is correct (well, mostly).
Revision 500: /trunk/SubversionPlugin/www
..
OldReleaseNotes.html
index.html
project_window.png
---
Powered by Subversion version 1.3.1 (r19032).
I find it useful to look at the output of an update to see what
chunks of the tree got updated but I have to search through the whole
list to see stuff I'm interested in instead of just knowing the
expected order.
curious,
stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Why do updated files come in "random" order?
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 5/22/06, Stephen Davis <su...@soundgeek.org> wrote:
> When I do an update, the files that come down are not in alphabetical
> order but are instead in a seemingly random order. Directories are
> also returned in non-alphabetical order.
>
> A www
> A www/project_window.png
> A www/index.html
> A www/OldReleaseNotes.html
> Updated to revision 500.
>
> This is obviously not a critical issue but it is visually
> disconcerting. I'm just wondering why svn works this way. When you
> browse the repository in your web browser it is correct (well, mostly).
> Revision 500: /trunk/SubversionPlugin/www
>
> ..
> OldReleaseNotes.html
> index.html
> project_window.png
> ---
> Powered by Subversion version 1.3.1 (r19032).
>
> I find it useful to look at the output of an update to see what
> chunks of the tree got updated but I have to search through the whole
> list to see stuff I'm interested in instead of just knowing the
> expected order.
There are a number of places in Subversion where the order files are
handled turns out to be dictated by unpredictable things like the
internal ordering of a hash table or something like that. There are
various issues that have been filed about making these kind of things
more predictable (for example, it's desireable for 'svn diff' output
to be in a predictable order so you can compare diffs). If you look
in the issue tracker you can probably find some issues that are
related to this.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org