On 1/2/14, 7:16 PM, James Hanley wrote:
> I've used the Rev keyword in some of our code, and we noticed that there may
> be
> a use case gap for the Rev/Revision and possibly Id keyword.
>
> As expected the keyword gets updated with any checkin, but there may be a need
> to have a merge-history a
I've used the Rev keyword in some of our code, and we noticed that there
may be a use case gap for the Rev/Revision and possibly Id keyword.
As expected the keyword gets updated with any checkin, but there may be a
need to have a merge-history aware version these keywords. Meaning that
the Rev sh
If you can separate out the twenty files that might be different between
the two projects - put them into a different folder for the "A"
application as well, and not just for "B" - then your process likely
gets even easier.
Then you can have the files in "B" be a straight up ongoing branch of
I'm part of a small development team (currently 4). We have two
applications used in-house that consist of about 1900 source files. The
two applications share about 1880 of the files in common, and there are
only about 20 different between them.
For a lot of complicated reasons I won't go int
On 1/1/14, 11:55 AM, Peter Flynn wrote:
> Apparently so; and this appears to be new (recent) behaviour. Quite why svn
> believes it needs to check the permissions one level above where it was told
> to
> go is unclear to me, but I'm sure wiser heads have thought this one through.
This is actually
