How have you setup your structure?
module/trunk
module/branches
If so, try:
*/trunk
Cheers / Erik
On Mon, May 17, 2010 at 11:50 PM, Erik Hemdal
wrote:
> I'm trying to solve what must be a trivial problem; yet I'm missing
> something -- probably very basic.
>
> Goal: Use mailer.py to email for
Hi folks.
I'm working on some code to automatically flow checkins from n
branches to m branches. Actually, I'm overhauling some old code for
doing this, mostly by rewriting.
The code I'm aiming to replace has had a longstanding problem with SVN
reliability. ISTR that one of the issues was that
Greetings,
We just upgraded from 1.3.1 to 1.6.9 (Woo hoo!) and put the new SVN on some
brand new servers. At the same time, we also setup some basic disaster
recovery using svnsync to mirror the commits from our primary SVN server to our
backup SVN server. I expected some performance degradat
I'm trying to solve what must be a trivial problem; yet I'm missing something
-- probably very basic.
Goal: Use mailer.py to email for all commits to trunk; send no email for
commits that do not change the trunk. I'm OK with being stupidly simple here,
so for example if someone changes branche
On Mon, May 17, 2010 at 03:41:22PM -0400, Eramo, Mark wrote:
> I am wondering if there is a simple way to script the checkout of only
> certain project folders in SVN without checking out others.
You want to create a "sparse working copy". Look at the --depth options
to update and checkout.
Note
I am wondering if there is a simple way to script the checkout of only certain
project folders in SVN without checking out others.
For example, I have all my projects setup with tags, branches and trunk folders
underneath the project name and I want to run a script that says go through the
proj
On Mon, May 17, 2010 at 2:33 PM, KARR, DAVID (ATTSI) wrote:
> I am forced to work with a SVN version on our server that is quite old,
> approximately 1.4.x. I use the latest Subversive version, but with the
> connector version that works with 1.4.x on the server. This combination
> works, but I
I am forced to work with a SVN version on our server that is quite old,
approximately 1.4.x. I use the latest Subversive version, but with the
connector version that works with 1.4.x on the server. This combination
works, but I'd like to understand some of the details underlying this.
I believe
On Mon, May 17, 2010 at 09:54:49AM -0300, Rodrigo Montenegro wrote:
> I still can't print the error message containing the wrong chars to the user.
>
> Subversion sends the following message:
>
> "[Error output could not be translated from the native locale to UTF-8.]"
See http://subversion.tigr
The code is quite long because I test other stuff beyond the chars, but I
can show you an short example that give us the same effect:
#!/usr/bin/python
import sys
import os
def dump(msg):
sys.stderr.write(str(msg) + '\n')
os.putenv('LANG','pt_BR.UTF8')
dump('รง')
sys.exit(1)
_
On May 17, 2010, at 07:54, Rodrigo Montenegro wrote:
> After I set the environment variable LANG to pt_BR.UTF8 the string of the
> filename seems to be correct since I do not have to process it anymore to
> compare to undesirable chars.
>
> The main goal has been achieved, the script is blockin
Ppl,
After I set the environment variable LANG to pt_BR.UTF8 the string of the
filename seems to be correct since I do not have to process it anymore to
compare to undesirable chars.
The main goal has been achieved, the script is blocking undesirable chars
but I still can't print the error messag
12 matches
Mail list logo
