Arnaud Charlet <[EMAIL PROTECTED]> wrote: > Not clear how to interpret this output without having to go to the doc, > no easy way to guess with my cvs knowledge, nor with my english knowledge. > > I guess I was expecting something more verbose ala cvs, e.g a real "status" > in english, such as up-to-date, locally modified, needs merge, ... > instead of "nothing" or "M" which are rather cryptic for a subversion > novice.
It's the same, with a minimal non-verbose output, and a default which does not require any connection to the server. You'll learn to use "svn status" without any argument to find out "what's up" in your working copy, irrespective of the server. If it does not say anything, your working copy is pristine. > $ svn status --show-updates Makefile.in > Status against revision: 105364 This would show pending updates as you expect. > Note: coming from a cvs background, having non incremental version numbers > *per file* is very disruptive and non intuitive. I suspect it will take > me some time to adjust to this. Any suggestions/tricks welcome. I don't think there are suggestions or tricks. You'll just have to get used to the idea that the changesets are atomic, and they uniquely identify the whole tree. When you said that your repository is version 105364, your svn status is empty, and you see a bug, I can download that very version and reproduce it, without having to match your top of ChangeLog, or other weird things. Per-file, you can see the history to see when the file was changed. Noice that you can use --verbose to see other files changed in the same commit, which is very handy (no more wasted time looking for the whole patch in gcc-cvs or in gcc-patches). > took between 16 and 22 seconds. 18 seconds typically. > > Now, did a cvs diff -r1.120 -r1.121 Makefile.in > > took between 3 and 5 seconds. 3.5 seconds typically. Out of curiosity, are you comparing anonymous CVS versus svn+ssh? In that case, it's apple and oranges. Do some ssh multiplexing and get speed back. > Is there any way to improve such svn diff operation ? (Note that > I frequently do cvs diff on arbitrary revisions, not just the last two, > although doing cvs diff -rHEAD is probably the most frequent operation > I rely upon). "svk" is a tool that lets you mirror the entire repository (or a subset of), checkout many copies from your local mirror, diff whatever with whatever, commit into your local repository, and finally push changes into the official repository. I believe it's going to be very handy for the average GCC developer. People are still discussing about it (see other mails) and I believe a Wiki page will be setup about it. -- Giovanni Bajo
