Hi,
I've noticed some differing behavior when using file externals and svn info
-r committed. I'm not sure what the expected behavior should be... hoping
to see what the masses think. I'm running svn 1.8.13 on Windows 7.
When I first create a file external and perform an update, the "svn info -
Mark:
Nice. And ClearCase with Dynamic Views as Brane reminded me.
Doug
On Fri, Jun 10, 2016 at 4:36 PM, Mark McKeown
wrote:
> Hi Doug,
>So if I remember correctly p4 supports this, when you "p4
> edit" a file it will tell you if anyone else has already done "p4 edit" on
> the
Hi Doug,
So if I remember correctly p4 supports this, when you "p4
edit" a file it will tell you if anyone else has already done "p4 edit" on
the file.
cheers
Mark
On Fri, Jun 10, 2016 at 8:15 PM, Doug Robinson
wrote:
> The dichotomy is due to the expression of "knowing who is ac
At least one problem with "svnsync" is that it, by design, does not
propagate the locks. So a sync'd repo cannot replace the sync'd-from
repository without losing all of the locks.
On Thu, Jun 2, 2016 at 9:28 AM, Daniel Shahaf
wrote:
> Michael Schwager wrote on Wed, Jun 01, 2016 at 09:58:18 -05
Agreed on ClearCase.
As for locking, it is normally considered "absolutely essential" for files
that "do not merge". Think checking in binaries. Or ugly generated XML
files (using unhappy algorithms). Pick your favorite non-merge-capable
file type(s). The point is to prevent multiple people fr
Jan:
Thanks for the note about CVS watches. I was unaware of that feature.
Interesting.
I agree, such a feature would tend to go directly against the requirements
for a DVCS.
Doug
On Mon, Jun 6, 2016 at 10:19 AM, Jan Keirse wrote:
>
> On Mon, Jun 6, 2016 at 3:47 PM, Doug Robinson
> wrote:
>
Brane:
You're right! ClearCase with dynamic views would provide that data (files
could not be modified unless checked out and the checkouts left markers in
the database). You could even see "who" from other replicas (assuming
proper synchronization).
Agreed: you could not see what changes they
The dichotomy is due to the expression of "knowing who is actually working
on a file".
I agree that if locking is used then (assuming nobody breaks the lock) you
know who will checkin next. And, yes, agreed, when they check in is a
social issue.
However, you really don't know who is working on t
