Whenever we merge code, many files in our codebase get updated
mergeinfo's with the new revision number, even though they were not
changed in this revision. From some searching online, this seems to
be a common situation, and it appears it might happen when not doing
merges from the root. There
I have a working copy with directories d1..dX in, and a repository to which
directories occasionally get added, say d1..dY where Y>X (though the
directory names are not numerical).
From the working copy, is there any way of telling what directories are
missing on that working copy? I don't want
David Brodie wrote:
> it is perfectly fine to remove the mergeinfos on files
> so long as the merginfos are preserved on the root folder, and that merges
> should always be done from the root to prevent mergeinfos from being set
> on individual files.
Yes, as long as the mergeinfo is identical, r
On May 26, 2011, at 14:52 , Alex Bligh wrote:
> I have a working copy with directories d1..dX in, and a repository to which
> directories occasionally get added, say d1..dY where Y>X (though the
> directory names are not numerical).
>
>> From the working copy, is there any way of telling what di
On Thu, May 26, 2011 at 01:52:56PM +0100, Alex Bligh wrote:
> I have a working copy with directories d1..dX in, and a repository to which
> directories occasionally get added, say d1..dY where Y>X (though the
> directory names are not numerical).
>
> >From the working copy, is there any way of tel
--On 26 May 2011 15:06:45 +0200 Stephen Butler wrote:
Have you tried the following?
svn status --show-updates --depth immediates
It tells you the names of the incoming items that an update would add
to the current working copy directory (as well as items that would be
modified).
Fantas
Hi Stefan,
Thanks, this is exactly what we needed. We appreciate your help.
Dave
-Original Message-
From: Stefan Sperling [mailto:s...@elego.de]
Sent: Sun 5/22/2011 8:26 AM
To: Dave Sailors
Cc: users@subversion.apache.org; David Austin
Subject: Re: How to display historic revisions afte
We have a lot of users using Subversion under Cygwin, which means that
any files they add get marked as executable by default (and almost
always uselessly). Is there any way to disable the automatic setting of
the svn:executable property on an "svn add"? The closest thing I see in
the manual is -
