tatus proj1/proj2-subdir", my svn will
accurately show the status of the "proj1/proj2-subdir" directory, but "svn
status proj1" never even looks at the "proj1/proj2-subdir" directory.
/Johan Holmberg
> **
>
> *From:* Johan Holmberg [mailto:johan...@gma
||proj2||
-
Note that the upgraded working copy has the externals entry marked
"unknown".
Is what I describe here a known problem of the "svn upgrade" command?
I also wonder if there is some way to get my existing working copies fully
functional again without doing a new checkout.
/Johan Holmberg
On 02/03/2012 05:57 PM, Stefan Sperling wrote:
On Fri, Feb 03, 2012 at 05:33:11PM +0100, Johan Holmberg wrote:
But here my working copy files are already UNIX text files (no \r\n
line endings).
Your working files might already be normalised according to the
setting of svn:eol-style, and
On 02/03/2012 05:54 PM, Philip Martin wrote:
Johan Holmberg writes:
A similar problem here, the file in the repository should have \n line
endings but the file has some \r\n line endings. Once again committing
the file should fix the problem (although mixed line endings may cause
the commit
On 02/03/2012 04:57 PM, Philip Martin wrote:
Johan Holmberg writes:
Yes, in one case I get a difference for the $Id$ line (from "svn diff"):
-$Id:$
+$Id$
OK. I think the file in the repository has '$Id:$' instead of '$Id$' for
the keyword. Committing t
On 02/03/2012 03:23 PM, Stefan Sperling wrote:
On Fri, Feb 03, 2012 at 03:04:54PM +0100, Johan Holmberg wrote:
On 02/03/2012 02:50 PM, Philip Martin wrote:
I have now done some further experiments. I just issued commands like this:
$ svn status # no modified files reported
On 02/03/2012 03:22 PM, Philip Martin wrote:
Johan Holmberg writes:
On 02/03/2012 02:50 PM, Philip Martin wrote:
I have now done some further experiments. I just issued commands like this:
$ svn status # no modified files reported
Subversion is not doing a full text
as modified.
Seems like a bug.
/Johan Holmberg
On 02/03/2012 02:09 PM, Philip Martin wrote:
Johan Holmberg writes:
So I don't think saying "If that timestamp differs from the one on
disk, the file is considered modified." is correct. "svn" does not
work like that for me at least.
You are correct, that is n
On 02/03/2012 01:28 PM, Stefan Sperling wrote:
On Fri, Feb 03, 2012 at 12:47:57PM +0100, Johan Holmberg wrote:
Is Subversion really sensitive to such timestamp differences?
Yes, it is. To avoid checking the entire content of all files in the
working copy every time you run 'svn diff
sion 1.6.12 (r955767)
rsync version 3.0.7 protocol version 30
ext4 file system
Regards,
/Johan Holmberg
11 matches
Mail list logo
