Re: Distributed Subversion Repositories

On Thu, Feb 18, 2010 at 03:59, Vincent Lefevre wrote: > On 2010-02-17 11:18:18 +, Julian Phillips wrote: >> If using a different tool is an option, then there are tools that let you >> interact directly with Subversion repositories from various other SCM >> tools, e.g. >> >> http://mercurial.s

Re: Distributed Subversion Repositories

On 2010-02-17 11:18:18 +, Julian Phillips wrote: > If using a different tool is an option, then there are tools that let you > interact directly with Subversion repositories from various other SCM > tools, e.g. > > http://mercurial.selenic.com/wiki/WorkingWithSubversion > http://flavio.castell

Re: Distributed Subversion Repositories

On 2010-02-17 11:10:12 +, Julian Phillips wrote: > You might want to take a look at svk, specifically: > > http://svk.bestpractical.com/view/UsingSVKAsARepositoryMirroringSystem svk is no longer maintained. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTM

Re: SVN Dump Question

Greetings, Justin Connell! > The reason, I'm asking such strange questions is that I have a very > abnormal situation on my hands here. I previously took a full dump of > the repo (for the reason you implied) where the original size of the > repo on disk was 150 GB, and the resulting dump file e

RE: Junior developers

Hi dcz, You can write a pre-commit hook or use AuthzSVNAccessFile to restrict commit into trunk by only Senior Developers. This way the Junior developer can perform his work in the branch and requests the Senior Developer to review and merge his code back into trunk in preparation for release. I a

RE: merging strategy

Hi Philipp, We use trunk as a stable stream. All work, feature or bug fix are performed on a branch. We merge back to trunk any changes that are ready for release. We also use trunk to propagate changes to all development teams. If you follow the above practise, then in your case, the bug fix i

Re: Junior developers

On Feb 17, 2010, at 08:36, dcz wrote: > Le 17/02/2010 15:24, Andy Levy a écrit : >> > >> There is no "dry run" for a commit. It's conceivable that you could >> check the user ID in the pre-commit, and if the committer is JD, >> reject the commit while mailing a diff to SD which represents the >

Re: merging strategy

On Wed, Feb 17, 2010 at 11:18 AM, Philipp Leusmann < philipp.leusm...@rwth-aachen.de> wrote: > > Am 17.02.2010 um 16:46 schrieb Rob van Oostrum: > > On Wed, Feb 17, 2010 at 9:09 AM, Philipp Leusmann < > philipp.leusm...@rwth-aachen.de> wrote: > >> Thank for you hint, Bob, but I have doubts this wa

Re: merging strategy

Am 17.02.2010 um 16:46 schrieb Rob van Oostrum: > On Wed, Feb 17, 2010 at 9:09 AM, Philipp Leusmann > wrote: > Thank for you hint, Bob, but I have doubts this way a merging works out for > us, since we are working in a small team without "voting" each task. So, I > have the fear, that changes

Re: merging trunk to branch merges the whole trunk history

On Wed, Feb 17, 2010 at 06:24:35AM -0800, Eli S wrote: > Once we upgrade, can I recover > using the same ideas? Do I have to mark the trunk in any way? > I don't think you need to do anything apart from upgrading the server. Subversion should be able to figure this out automatically. It just need

Re: merging strategy

On Wed, Feb 17, 2010 at 9:09 AM, Philipp Leusmann < philipp.leusm...@rwth-aachen.de> wrote: > Thank for you hint, Bob, but I have doubts this way a merging works out for > us, since we are working in a small team without "voting" each task. So, I > have the fear, that changesets committed to trunk

Re: merging strategy

Thank for you hint, Bob, but I have doubts this way a merging works out for us, since we are working in a small team without "voting" each task. So, I have the fear, that changesets committed to trunk contain unrelated changes, which by accident make it into the branch. So, it would be nice to

Re: Junior developers

Le 17/02/2010 15:24, Andy Levy a écrit : On Wed, Feb 17, 2010 at 09:19, dcz wrote: Thanks for responding. I was hopping that someone did put something together to handle this. It looks like doable with a pre-commit hook that would have a look in a db (or a file) to find out if the user is

Re: Junior developers

On Wed, Feb 17, 2010 at 09:19, dcz wrote: > Thanks for responding. > > I was hopping that someone did put something together to handle this. > It looks like doable with a pre-commit hook that would have a look in a db > (or a file) to find out if the user is JD or SD. For JDs, the commit could > b

Re: merging trunk to branch merges the whole trunk history

Stefan Sperling wrote: On Tue, Feb 16, 2010 at 10:42:59PM -0800, Eli S wrote: Apologies to for letting this languish. I was waiting on an upgrade and the system administrators upgraded to 1.6.6 on Ubuntu. The repository and branch were created on 1.5.1 using cvs2svn. The branch was created us

Re: Junior developers

Thanks for responding. I was hopping that someone did put something together to handle this. It looks like doable with a pre-commit hook that would have a look in a db (or a file) to find out if the user is JD or SD. For JDs, the commit could be made dry-run, and the script could in such case s

Re: Junior developers

On Wed, Feb 17, 2010 at 08:17, dcz wrote: > Hello, > Here is what I'm trying to do : some user (let's call them junior developer) > should require their commit to be authorized by other (senior developer) > before they would actually be committed. > > Since I saw this feature on an svn (though I d

Junior developers

Hello, Here is what I'm trying to do : some user (let's call them junior developer) should require their commit to be authorized by other (senior developer) before they would actually be committed. Since I saw this feature on an svn (though I do not administrate this one, so I can't tell how

Merge tracking questions

Hi I'm looking into moving from svn 1.4.x to svn 1.6.x and migrate from svnmerge.py merge tracking to core svn merge tracking. I'm now investigating how to merge feature branches. I'd like to merge a branch to the trunk and continue work in the branch. I've found two alternatives 1. merge --rein

Re: Expected release date of RedBean for 1.6

On Tue, Feb 16, 2010 at 09:42:25PM -0500, Pat Farrell wrote: > While SVN seems to have an active support community, I'm not seeing > parallel evidence of active support for the documentation. > > for example, in another thread, Mike Dixon wrote: > > Uh? What's wrong with --reintegrate? > > Well f

Re: Distributed Subversion Repositories

On Wed, Feb 17, 2010 at 11:08, Mark wrote: > I have the following problem. Repository A is used by a lab of developers. 1 > developer needs to work off site against the code base held in A, for an > extended period of time. He requires version control, but cannot gain access > to Repository A. To

Re: how do I post a feature request? (svn status -r 400:401)

On Wed, Feb 17, 2010 at 04:39, mlg 3 wrote: > I want to obtain a list of files that have changed between two versions. > > If it was a working copy, I could use > svn status > and > svn diff > > With two versions in the repository, I can still use > svn diff -r 400:401 > but cannot use > svn statu

Re: Distributed Subversion Repositories

On Feb 17, 2010, at 05:31, Tennebø Frode wrote: > You could use vendor branches > (http://svnbook.red-bean.com/en/1.0/ch07s04.html). Let's not refer people to the ancient 1.0 version of the book. The most recent final version of this documentation currently available is: http://svnbook.red-be

RE: Distributed Subversion Repositories

> I have the following problem. Repository A is used by a lab > of developers. 1 developer needs to work off site against the > code base held in A, for an extended period of time. He > requires version control, but cannot gain access to > Repository A. To solve this we can dump/mirror A into

RE: Where is the latest SVN 1.6.9 binary for stable debian?

Hi, Pat Farrell wrote: > My debian server is running Lenny, the latest and greatest debian. > > The svn version is svn, version 1.5.1 (r32289) > I'd like to be running 1.6.9 > I can't find the .deb files, or better, a good repository to add to my > /etc/apt sources.list. 1.6.4 is available in the

Re: Distributed Subversion Repositories

On Wed, 17 Feb 2010 12:09:02 +0100, Stefan Sperling wrote: > On Wed, Feb 17, 2010 at 10:08:12AM +, Mark wrote: >> I have the following problem. Repository A is used by a lab of >> developers. 1 developer needs to work off site against the code base >> held in A, for an extended period of time.

Re: Distributed Subversion Repositories

On Wed, 17 Feb 2010 10:38:19 +, Mark wrote: > I have the following problem. Repository A is used by a lab of > developers. 1 developer needs to work off site against the code base > held in A, for an extended period of time. He requires version control, > but cannot gain access to Repositor

Re: Distributed Subversion Repositories

On Wed, Feb 17, 2010 at 10:08:12AM +, Mark wrote: > I have the following problem. Repository A is used by a lab of > developers. 1 developer needs to work off site against the code base > held in A, for an extended period of time. He requires version > control, but cannot gain access to Reposit

Distributed Subversion Repositories

I have the following problem. Repository A is used by a lab of developers. 1 developer needs to work off site against the code base held in A, for an extended period of time. He requires version control, but cannot gain access to Repository A. To solve this we can dump/mirror A into repository

Distributed Subversion Repositories

I have the following problem. Repository A is used by a lab of developers. 1 developer needs to work off site against the code base held in A, for an extended period of time. He requires version control, but cannot gain access to Repository A. To solve this we can dump/mirror A into repository

Re: how do I post a feature request? (svn status -r 400:401)

On Wed, Feb 17, 2010 at 10:56:38AM +0100, Stefan Sperling wrote: > On Wed, Feb 17, 2010 at 01:39:44AM -0800, mlg 3 wrote: > > I want to obtain a list of files that have changed between two versions. > > > > If it was a working copy, I could use > > svn status > > and > > svn diff > > > > With two

Re: how do I post a feature request? (svn status -r 400:401)

On Wed, Feb 17, 2010 at 01:39:44AM -0800, mlg 3 wrote: > I want to obtain a list of files that have changed between two versions. > > If it was a working copy, I could use > svn status > and > svn diff > > With two versions in the repository, I can still use > svn diff -r 400:401 > but cannot use

how do I post a feature request? (svn status -r 400:401)

I want to obtain a list of files that have changed between two versions. If it was a working copy, I could use svn status and svn diff With two versions in the repository, I can still use svn diff -r 400:401 but cannot use svn status -r 400:401 And: it would be valuable to have a switch for file

Re: merging trunk to branch merges the whole trunk history

On Tue, Feb 16, 2010 at 10:42:59PM -0800, Eli S wrote: > Apologies to for letting this languish. I was waiting on an upgrade > and the system administrators upgraded to 1.6.6 on Ubuntu. The > repository and branch were created on 1.5.1 using cvs2svn. The > branch was created using svn copy between

Re: Expected release date of RedBean for 1.6

On Wed, Feb 17, 2010 at 12:36:19AM -0500, Pat Farrell wrote: > I've never yet found a good developer who is good at writing > documentation. I've been doing this for nearly 40 years. I do actually tend to like writing documentation sometimes. No idea if it's really any good. But I've been contribu