On Tue, Dec 20, 2011 at 07:04:32PM -0500, Karl Wright wrote:
> Log file attached.
> Karl
Hi Karl,
Version: 1.6.12 (SlikSvn/1.6.12) WIN32, compiled Jun 22 2010, 20:45:23
You're running a known-bad version of the SlikSvn binaries.
Please upgrade.
See http://svn.haxx.se/users/archive-2010-09/0065.
On Dec 20, 2011, at 06:08, Mojca Miklavec wrote:
> I'm writing a script (also used as a cron job on the server) that
> should work independent of whether or not a checkout has already been
> done or not. I would like to do "repeated sparse checkout" as
> explained below, but I'm not sure how to do
On Wed, Dec 21, 2011 at 06:07:05AM -0600, Ryan Schmidt wrote:
> On Dec 20, 2011, at 06:08, Mojca Miklavec wrote:
> > Is there any way to prevent
> > deleting existing contents within the scope of command line arguments?
> > A workaround is to use something like
> >if [ ! -d "project" ]; then
>
Setting LC_ALL=C does not work either. Wonder why it works for v1.7 but
not for v1.6. Again, I'm getting "svn: Compression of svndiff data failed"
when executing "svn co svn://path/to/repo/prj working_directory". But if I
do a "svn co file:///" then it's okay for v1.6.
On Tue, Dec 20, 2011
On Wed, Dec 21, 2011 at 07:47:16AM -0500, Phil wrote:
> Setting LC_ALL=C does not work either. Wonder why it works for v1.7 but
> not for v1.6. Again, I'm getting "svn: Compression of svndiff data failed"
> when executing "svn co svn://path/to/repo/prj working_directory". But if I
> do a "svn co
I have about 155 packages in the repository that I want to checkout. This
has never worked with v1.6. The workaround is to checkout each package one
at a time (svn co svn://). As you can see, that's very tedious. I assume
subversion doesn't care how many packages are in my repository. I did th
Maybe I should download and get a better zlib package. Let me try and keep
everyone posted.
On Wed, Dec 21, 2011 at 9:14 AM, Phil wrote:
> I have about 155 packages in the repository that I want to checkout. This
> has never worked with v1.6. The workaround is to checkout each package one
> a
On Wed, Dec 21, 2011 at 13:21, Stefan Sperling wrote:
> On Wed, Dec 21, 2011 at 06:07:05AM -0600, Ryan Schmidt wrote:
>> On Dec 20, 2011, at 06:08, Mojca Miklavec wrote:
>> > Is there any way to prevent
>> > deleting existing contents within the scope of command line arguments?
>> > A workaround is
Season's greetings all!
I'm using svnsync to copy our repositories for the FIRST time to a mirror site
and running out of space, somewhere.
From: RH ES 4, Update 5 32-bit server
To: CentOS Release 5.5, 64-bit server
I tried to watch the disk partitions with a df -h and the numbers never changed
I should have mentioned that I'm using Subversion 1.6.4 on the source side and
Subversion 1.6.17 on the destination side.
-Original Message-
From: Curley, John [mailto:john.cur...@windriver.com]
Sent: Wednesday, December 21, 2011 1:58 PM
To: users@subversion.apache.org
Subject: Problem
One of my common use cases for subversion is to want to split my changes into
two separate commits. In the past, I would do the following:
1) Check out
2) Make changes
3) Realize that this should be more than one commit
4) Copy directory "MyCode" to "MyCode2"
5) Rev
Randon,
On Wed, Dec 21, 2011 at 3:10 PM, Randon Spackman <
randon.spack...@hotdocs.com> wrote:
> One of my common use cases for subversion is to want to split my changes
> into two separate commits. In the past, I would do the following:
>
> ** **
>
> **1) **Check out
>
> **2)
Sounds like a feature much like git's "git stash"
On 21 December 2011 20:10, Randon Spackman wrote:
> One of my common use cases for subversion is to want to split my changes
> into two separate commits. In the past, I would do the following:
>
>
>
> 1) Check out
>
> 2) Make changes
>
Hmm... It's close, but the limitations on only assigning one per file are a
bit onerous; it's very often in the same file that I'm working on that I find
bugs, etc., that I want to commit separately.
Randon
From: Chris Shelton [mailto:cshel...@shelton-family.net]
Sent: Wednesday, December 21,
Well, it turns out that the other application does not support svn v1.7 but
only v1.6. Too bad I still cannot get v1.6 to perform massive checkout
using the "svn co svn://..." syntax. I guess I would have to write a unix
shell script to help speed up my manual process. What I'm doing is first
pe
https://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/svn-viewspec.py
Phil wrote on Wed, Dec 21, 2011 at 16:44:36 -0800:
> Well, it turns out that the other application does not support svn v1.7 but
> only v1.6. Too bad I still cannot get v1.6 to perform massive checkout
> using th
Daniel,
Please forgive me but I'm not familiar with *.py
On Wed, Dec 21, 2011 at 7:52 PM, Daniel Shahaf wrote:
>
> https://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/svn-viewspec.py
>
>
> Phil wrote on Wed, Dec 21, 2011 at 16:44:36 -0800:
> > Well, it turns out that the other ap
On 12/21/2011 4:31 PM, Randon Spackman wrote:
Hmm... It's close, but the limitations on only assigning one per file
are a bit onerous; it's very often in the same file that I'm working
on that I find bugs, etc., that I want to commit separately.
Randon
Normally I have one "main" sandbox
On Dec 21, 2011, at 19:01, Phil wrote:
> Please forgive me but I'm not familiar with *.py
It's a Python script.
http://en.wikipedia.org/wiki/Python_%28programming_language%29
On Dec 21, 2011, at 14:10, Randon Spackman wrote:
> I’d like to see a new svn command such as “svn localize” (don’t keep my
> terminology if it sucks) that would make the directory you specify its own
> independent working copy that can be copied and manipulated individually,
This function has
20 matches
Mail list logo
