On Tue, Dec 14, 2010 at 4:58 PM, Ryan Schmidt
wrote:
> On Dec 14, 2010, at 15:48, r...@elilabs.com wrote:
>
>>> If you want to know what version of mod_dav_svn is installed on the
>>> server, that can actually be determined from the client, by accessing the
>>> repository's http or https URL in a
On Dec 14, 2010, at 15:48, r...@elilabs.com wrote:
>> If you want to know what version of mod_dav_svn is installed on the
>> server, that can actually be determined from the client, by accessing the
>> repository's http or https URL in a web browser. (In fact, I'm not sure
>> how to find out the v
On Dec 14, 2010, at 09:32, Ludwig, Michael wrote:
>> on command prompt type svn --version and you will get the required info
>
> That's for the client.
>
> The OP asked how to get the version of the server from the clientside.
> (So without access to the serverside.)
Actually, he didn't speci
On Tue, Dec 14, 2010 at 04:35:59PM +0100, Thorsten Schöning wrote:
> Guten Tag Mauro Condarelli,
> am Dienstag, 14. Dezember 2010 um 15:34 schrieben Sie:
>
> > I would rather not checkout a fresh copy, move all changes to it and
> > submit that, if possible, because it is too error-prone.
>
> Som
Guten Tag Mauro Condarelli,
am Dienstag, 14. Dezember 2010 um 15:34 schrieben Sie:
> I would rather not checkout a fresh copy, move all changes to it and
> submit that, if possible, because it is too error-prone.
Some weeks ago I had the same situation, two times within one week,
and I didn't fin
On 12/14/2010 9:09 AM, Andy Levy wrote:
On Tue, Dec 14, 2010 at 09:34, Mauro Condarelli wrote:
Hi,
This should be a FAQ, but I didn't find a proper answer, so here I am.
I suffered a crash in my SVN server machine.
I had a slightly old version of the repository on my backup disks.
I have a f
> on command prompt type svn --version and you will get the required info
That's for the client.
The OP asked how to get the version of the server from the clientside.
(So without access to the serverside.)
I naively tried the following, but it doesn't reveal the version info:
l...@hrswks006:
On Tue, Dec 14, 2010 at 8:49 PM, K F wrote:
> This is just a simple question that I can't find the answer to. How do I go
> about finding out what version of subversion (e.g. 1.6.#) is on the server.
> The svn help doesn't give that type of information and there is no 'about'
> that usually has t
This is just a simple question that I can't find the answer to. How do I go
about finding out what version of subversion (e.g. 1.6.#) is on the server. The
svn help doesn't give that type of information and there is no 'about' that
usually has that info.
Thanks,
Rich
On Tue, Dec 14, 2010 at 09:34, Mauro Condarelli wrote:
> Hi,
> This should be a FAQ, but I didn't find a proper answer, so here I am.
>
> I suffered a crash in my SVN server machine.
> I had a slightly old version of the repository on my backup disks.
> I have a few modified working copies.
>
> I
Hi,
This should be a FAQ, but I didn't find a proper answer, so here I am.
I suffered a crash in my SVN server machine.
I had a slightly old version of the repository on my backup disks.
I have a few modified working copies.
I restored the server and the repository.
All *seemed* ok, but, unfort
Danny Trebbien gmail.com> writes:
>
> > I must be missing something here, is this patch applied to the current SVN
source?
> >
> > I have downloaded SVN 1.6.15 source from Tigris.org, and cant find the
changes in the source. Also this
> patch is applied to a file : subversion/svnsync/sync.c but
Guten Tag Nick Stolwijk,
am Dienstag, 14. Dezember 2010 um 12:03 schrieben Sie:
> Another easy one. ;)
Using separate repositories for projects makes access control a lot
easier and safer: Depending on using svnserve, one has the chance to
use different instances for svnserve on different ports f
You cannot easily refactor code into seperate modules, used by
multiple projects, with keeping of history.
Another easy one. ;)
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Tue, Dec 14, 2010 at 11:02 AM,
On Tue, Dec 14, 2010 at 11:58 AM, Cooke, Mark wrote:
>> On Tuesday 14 December 2010, Cooke, Mark wrote:
>> > I'd be interested in any strong arguments for using one
>> > repo over many!
>>
>> -Original Message-
>> From: Ulrich Eckhardt [mailto:ulrich.eckha...@dominolaser.com]
>> Sent: 14 D
> On Tuesday 14 December 2010, Cooke, Mark wrote:
> > I'd be interested in any strong arguments for using one
> > repo over many!
>
> -Original Message-
> From: Ulrich Eckhardt [mailto:ulrich.eckha...@dominolaser.com]
> Sent: 14 December 2010 10:53
> To: users@subversion.apache.org
> Sub
On Tuesday 14 December 2010, Cooke, Mark wrote:
> I'd be interested in any strong arguments for using one repo over many!
You don't need svnadmin to create a new project.
That was simple! :'D
Uli
--
ML: http://subversion.apache.org/docs/community-guide/mailing-lists.html
FAQ: http://subversion
> -Original Message-
> From: Johan Corveleyn [mailto:jcor...@gmail.com]
> Sent: 13 December 2010 20:04
> To: users@subversion.apache.org
> Subject: Archiving Projects (End-Of-Life)
>
> Hi,
>
> I'm wondering if there is a (de-facto) standard way of "end-of-lifing"
> projects in an SVN rep
2010/12/14 Ryan Schmidt :
> On Dec 13, 2010, at 04:27, Norbert Unterberg wrote:
>
>> We have a project that contains a few svn:externals which point into
>> the same repository (using ../ or ^/ syntax).
>> Problem is that when we need to go back in time with the project for
>> some reason and do an
>
Linedata Limited
Registered Office: 85 Gracechurch St., London, EC3V 0AA
Registered in England and Wales No 3475006 VAT Reg No 710 3140 03
-Original Message-
> From: Johan Corveleyn [mailto:jcor...@gmail.com]
> Sent: 13 December 2010 20:04
> To: users@subversion.apache.org
> Subject:
20 matches
Mail list logo
