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

Monitoring upstream sources after re-committing to a new repository?

From: Marcus Crafter <crafterm_at_gmail.com>
Date: 2005-12-12 19:57:13 CET

Hi All,

Hope all is going well.

We're about to start using a product available via Subversion as the
base for a new project. Since we're using Subversion internally, I'd
like to be able to take the remote sources and check them in locally so
that we can work on them and (due to the structure of the project)
modify them.

Once we've committed the sources locally, is there any way we can still
monitor the original upstream repository for changes? and import them
as we'd like?

I'm not sure if Subversion offers such a feature but any process that
would allow us to do this would be great (ie. modify the sources and
check them in locally, but still monitor the remote repository for

The only way I can think of doing this is via patches, but I'd rather
not maintain patches to the external sources as if they change
regularly we'll be needing to update our patches more often than what
we'd like.

Any thoughts? Has anyone had this requirement before at all?



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 12 20:18:03 2005

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