Knut, you made the right assumptions and helped me in my confusion.
I'm using subclipse and wondered that the project has revision
210019 whereas the build.xml for example has revision 208713.
This contradicted my understanding of subversion revisioning, but
is the 'fault' of subclipse.
I wonder if one can configure the working revision (last revision
a file was updated from) as label decoration too.
Achim
Am Thu, 14 Jul 2005 08:48:55 +0200 schrieb Knut Wannheden
<[EMAIL PROTECTED]>:
Achim,
What exactly do you mean by mixed revision numbers? I believe that the
revision numbers indicated in Eclipse (using Subclipse plugin) next to
the filenames denote the last revision in which the file in question
was changed. That's what you'd also see printed in the third column by
a "svn stat -v".
--knut
On 7/13/05, Achim Hügen <[EMAIL PROTECTED]> wrote:
I'm a little bit confused with regard to the subversion revisions.
The project files have mixed revision numbers after a clean checkout or
a
svn update.
As I understand the subversion book this could happen after a
commit but after an "svn update" all files should have the same (global)
revision.
I haven't found any info on the subversion site concerning this issue.
Does anybody knows an answer?
Achim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
