Hi All
We are using 1.6 SVN.
We like to svn merge from our branch A to trunk.
We have been diligent in svn merge from trunk to A.
These svn merges from trunk to branch A also include --record-only merges
too, in addition to regular merges.
Development on branch A has stopped.
Now we like to merge
Hi,
It seems like issue #4425 [1] which is fixed in r1522892 and proposed
for backport to Subversion
1.8.4.
I tried the nightly build of TortoiseSVN [1]
svn, version 1.8.4-dev (under development)
compiled Oct 16 2013, 23:05:56 on x86-microsoft-windows
(as I was not able to compile the
W dniu 2013-10-14 22:01, Bob Archer pisze:
W dniu 2013-10-04 15:04, Ivan Zhakov pisze:
On 4 October 2013 17:00, Karol Szkudlarek ka...@mikronika.com.pl
wrote:
W dniu 2013-10-04 14:50, Ivan Zhakov pisze:
On 4 October 2013 16:44, Ivan Zhakov i...@visualsvn.com wrote:
I'm trying to use the
Hi all,
We are actively using authz path-based authentication rules: due to some legal
requirements, some parts of our product source code are not accessible to a
part of the developer team. Currently authz does not support wildcards (there
is an issue about that [1] discussed since 2006).
Hi All
We are using 1.6 SVN.
We like to svn merge from our branch A to trunk.
We have been diligent in svn merge from trunk to A.
These svn merges from trunk to branch A also include --record-only merges
too, in addition to regular merges.
Development on branch A has stopped.
Now we like
1. You can use svn merge --dry-run if you are using command line or if you
are using a client like tortoise then a test merge option should be available.
This won't actually merge but show if there will be any failure in case an
actual merge was performed.
2. Do the re-intergrate
Hi All
We are using 1.6 SVN.
We like to svn merge from our branch A to trunk.
We have been diligent in svn merge from trunk to A.
These svn merges from trunk to branch A also include --record-only merges
too, in addition to regular merges.
Development on branch A has stopped.
Now we like
[Restored CC of the mailing list]
On Thursday, October 17, 2013 03:24:45 PM Mark Phippard wrote:
On Thu, Oct 17, 2013 at 3:00 PM, Alexey Neyman sti...@att.net[1] wrote:
We are actively using authz path-based authentication rules: due to some
legalrequirements, some parts of our product
On Thu, Oct 17, 2013 at 5:39 PM, Alexey Neyman sti...@att.net wrote:
**
[Restored CC of the mailing list]
Did I only reply to you? Thanks for adding the list back.
On Thursday, October 17, 2013 03:24:45 PM Mark Phippard wrote:
So your question is whether at a certain size does it
On 17.10.2013 18:08, Karol Szkudlarek wrote:
W dniu 2013-10-14 22:01, Bob Archer pisze:
W dniu 2013-10-04 15:04, Ivan Zhakov pisze:
On 4 October 2013 17:00, Karol Szkudlarek ka...@mikronika.com.pl
wrote:
W dniu 2013-10-04 14:50, Ivan Zhakov pisze:
On 4 October 2013 16:44, Ivan Zhakov
On 17.10.2013 20:00, Alexey Neyman wrote:
Hi all,
We are actively using authz path-based authentication rules: due to some
legal
requirements, some parts of our product source code are not accessible to a
part of the developer team. Currently authz does not support wildcards (there
is
On Friday, October 18, 2013 02:46:39 AM Branko Čibej wrote:
On 17.10.2013 20:00, Alexey Neyman wrote:
Hi all,
We are actively using authz path-based authentication rules: due to some legal
requirements, some parts of our product source code are not accessible to a
part of the developer
12 matches
Mail list logo
