Hello!
(This is TortoiseSVN's command line client
svn, version 1.7.7 (r1393599)
compiled Oct 8 2012, 18:39:05,
belonging to
TortoiseSVN 1.7.10, Build 23359 - 32 Bit , 2012/10/08 11:46:26
on Windows XP, if that makes a difference)
I deleted a file a.txt in revision 1186.
sv
On Thu, Nov 08, 2012 at 03:15:49PM +0100, Niemann, Hartmut wrote:
> Hello!
>
> (This is TortoiseSVN's command line client
>svn, version 1.7.7 (r1393599)
>compiled Oct 8 2012, 18:39:05,
> belonging to
>TortoiseSVN 1.7.10, Build 23359 - 32 Bit , 2012/10/08 11:46:26
> on Windows XP,
Hi
I've notices a change in the svn info output when I have a tree conflict.
The left and right are from the same branch. Is this correct? (svn 1.7
client to 1.6 server).
kiren@Pillay2:~/Documents/workspace-TRUNK/newServer$ svn info
business_services/pams-bs-subscriber-account/src/main/java/za/co
Hi,
I am looking for some guidance on where to store build artifacts in SVN.
Our projects are organized in the typical fashion:
/trunk/Customer1/
../../src
../../database
/branch
/tags
/release
Our official build server is a QNX system, a Unix-like OS.
Our proposed process ca
On Thu, Nov 08, 2012 at 05:52:07PM +0200, Kiren Pillay wrote:
> Hi
>
> I've notices a change in the svn info output when I have a tree conflict.
What change did you notice? You're only showing one instance of output.
What has changed? And which releases of Subversion are you comparing?
> The lef
Just my two cents, but I think that "release" should only refer to builds that
have been shipped to the end-user and are in usage.
Why not have a top-level directory:
/build
And if it's automated to build every night, it could have:
/build/9 November 2012/...
/build/8 November 2012/...
/
--
__
Thanks and Regards
Sergey Chekotilo
Cell:+380913194550
svn-crash-log20121108233205.dmp
Description: Binary data
svn-crash-log20121108233205.log
Description: Binary data
On Thu, Nov 08, 2012 at 11:40:08PM +0200, Sergey Chekotilo wrote:
> Thanks and Regards
> Sergey Chekotilo
This is a known bug in 1.7.7 which happens only on Windows.
Due to a coding error, when a user name is already cached and
the --username option specifies a different user name than the
one in
Guten Tag Ahmed, Omair (GE Oil & Gas),
am Donnerstag, 8. November 2012 um 23:39 schrieben Sie:
> Our proposed process calls for the build engineer to copy the code
> from the SVN repo to the build server. When a build has been
> executed, where should we copy the artifacts (the executables) back
>