Re: Problem getting new external into my working copy

2012-02-21 Thread Michael Hartmeier
Having "svn up " seems like a proper solution for me. Do you want me to file a feature request or bug report? As a work-around, I'll try Philip's fixed revsions. Thank you all! Michael Am 20.02.2012 16:33, schrieb Stefan Sperling: On Mon, Feb 20, 2012 at 02:49:54PM +0100, Michael Hartmeier wr

Re: Problem getting new external into my working copy

2012-02-21 Thread Philip Martin
Michael Hartmeier writes: > Having "svn up " seems like a proper solution for me. > Do you want me to file a feature request or bug report? Yes, please raise an issue. -- Philip

digest mode

2012-02-21 Thread e-letter
Readers, For the benefit of novices, it seems that there is a digest-mode for this mailing list: users-digest@..., however, this is not stated clearly on the web page. Also the automatic subscription confirmation message states that submissions should be to 'users-digest@...' and not 'users@...':

use hotcopy or dump for network repository

2012-02-21 Thread e-letter
Readers, The manual states that 'hotcopy' of 'dump' are examples of commands to use to create a copy of a repository. An svn repository was created on a network using the protocol 'svn+ssh'; what is the most appropriate method to make a copy (e.g. onto a CD) and then use that copy to transfer that

Re: use hotcopy or dump for network repository

2012-02-21 Thread Les Mikesell
On Tue, Feb 21, 2012 at 11:18 AM, e-letter wrote: > Readers, > > The manual states that 'hotcopy' of 'dump' are examples of commands to > use to create a copy of a repository. An svn repository was created on > a network using the protocol 'svn+ssh'; what is the most appropriate > method to make

RE: Branching/Merging Strategy

2012-02-21 Thread leojhartiv
Thanks for your responses! I guess the part I'm missing is how you would support hotfixes, etc? If I don't always branch off of trunk (production), how can I be sure I'm only releasing the small changes to support the hotfix, versus all the other changes being worked on for a larger development

Re: use hotcopy or dump for network repository

2012-02-21 Thread Nico Kadel-Garcia
On Tue, Feb 21, 2012 at 12:37 PM, Les Mikesell wrote: > On Tue, Feb 21, 2012 at 11:18 AM, e-letter wrote: > >> Readers, >> >> The manual states that 'hotcopy' of 'dump' are examples of commands to >> use to create a copy of a repository. An svn repository was created on >> a network using the pro

RE: Branching/Merging Strategy

2012-02-21 Thread leojhartiv
As a follow-up, strategy #2 seems to describe what my team is doing: http://blogs.collab.net/subversion/2007/11/branching-strat/ leojhartiv wrote: > > Thanks for your responses! > > I guess the part I'm missing is how you would support hotfixes, etc? If I > don't always branch off of trunk (

RE: Branching/Merging Strategy

2012-02-21 Thread Bob Archer
> Thanks for your responses! > > I guess the part I'm missing is how you would support hotfixes, etc? If I > don't > always branch off of trunk (production), how can I be sure I'm only releasing > the small changes to support the hotfix, versus all the other changes being > worked on for a large

svn:externals parser API

2012-02-21 Thread Nikolaus Demmel
Hi, this is my first post to this list and I'm not subscribed, so please CC me when answering. I'm investigating how to improve using git-svn with svn-externals, either with an additional script or directly in within git. In any case I would need git-svn to display the externals. There is "git sv

RE: Branching/Merging Strategy

2012-02-21 Thread
> -Original Message- > From: leojhartiv [mailto:leo.h...@gmail.com] > Sent: Tuesday, February 21, 2012 11:49 AM > To: users@subversion.apache.org > Subject: RE: Branching/Merging Strategy > > > As a follow-up, strategy #2 seems to describe what my team is doing: > http://blogs.collab.net/

Re: svn:externals parser API

2012-02-21 Thread Stefan Sperling
On Tue, Feb 21, 2012 at 10:26:34PM +0100, Nikolaus Demmel wrote: > Hi, > > this is my first post to this list and I'm not subscribed, so please CC > me when answering. > > I'm investigating how to improve using git-svn with svn-externals, > either with an additional script or directly in within g

Re: svn:externals parser API

2012-02-21 Thread Stefan Sperling
On Tue, Feb 21, 2012 at 11:50:54PM +0100, Stefan Sperling wrote: > I think svn_wc_parse_externals_description3() should do what you need. > Does this help you? > > The function is mapped in the python bindings: > > >>> import svn.wc > >>> svn.wc.svn_wc_parse_externals_description3 > Hmmm... my

Multiple conflicts while postponing conflict resolution across multiple merged commits

2012-02-21 Thread Rick Ramstetter
Hi all, A question regarding the handling of multiple conflicts while postponing conflict resolution across multiple merged commits. Let's say I merge two commits from trunk to a branch: $ cd /pathto/branch $ svn merge svn://repo/trunk -c 1,2 --accept=postpone Each of those merged commits (c1 an

hot-backup.py

2012-02-21 Thread Salari, Kamran
Hi everyone, I am new to Subversion, and I am using TortoiseSVN-1.7.3 and Slik-Subversion-1.7.2 on my XP system (Service Pack 3). I would like to know if there is a Windows version of "hot-backup.py" which I can use. It appears the script in "tools\backup" is written for a Unix environment.

Re: Multiple conflicts while postponing conflict resolution across multiple merged commits

2012-02-21 Thread Stefan Sperling
On Tue, Feb 21, 2012 at 04:48:12PM -0800, Rick Ramstetter wrote: > Hi all, > > A question regarding the handling of multiple conflicts while > postponing conflict resolution across multiple merged commits. > > Let's say I merge two commits from trunk to a branch: > $ cd /pathto/branch > $ svn mer

Re: hot-backup.py

2012-02-21 Thread Nico Kadel-Garcia
On Tue, Feb 21, 2012 at 7:27 PM, Salari, Kamran wrote: > Hi everyone, > > ** ** > > I am new to Subversion, and I am using TortoiseSVN-1.7.3 and > Slik-Subversion-1.7.2 on my XP system (Service Pack 3). I would like to > know if there is a Windows version of “hot-backup.py” which I can use.