[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Encapsulating internal diffs?

From: Jim Sokoloff <jim_at_sokoloff.com>
Date: 2007-05-18 12:32:55 CEST

On Thu, 17 May 2007, H. S. Teoh wrote:

> Any suggestions as to how to improve this? The CM process is
> unfortunately unlikely to change---they still want us to submit diffs
> rather than have direct commit access. But it would greatly help things
> if there is a way of encapsulating a diff that effectively tells SVN,
> "file X is actually derived from internal_url#1, so when adding please
> reuse the history from that URL". Ideas?

Have you considered giving the development team
direct access to subversion repository Y (or
path Z within repository X) and having the CM
team using repository X directly?

I presume your development team wants to have
revision control before involving CM anyway, so
if you adopt a model like this, you may be able
to easily automatically generate the diffs and
ancestry information to feed CM from your svn
history in the development repository.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 18 12:33:20 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.