What would be the best way to create "working repositories"?
From: Tom Malia <tommalia_at_ttdsinc.com>
Date: Tue, 29 Jun 2010 08:54:28 -0400
I'm looking for an easy way to allow programmers on a large project to
It appears that all this would be pretty simple if they literally did just
The scenario I'm thinking of is one in which there's a main company that
One thought I had, that I'd like to know if there's an easy way to do it or
I'd like to be able to:
1) "export" sections of the "main" repository
2) Then add the directories that were just exported to a repository
3) Check out the stuff just added to the "working repo" to a "working
4) Developer does their development in this WC, checking things into
5) When the developer feels they are ready to "merge" their work back
a. Check out the equivalent section of the "main" repo to a separate
b. Delete everything from that WC
c. Copy everything from the "WC" that came from their "Working repo"
d. Diff the current files in the "main" WC against the current version
e. Check the WC from the "main" repo back into main
f. Delete all WC folders from their local machine
g. Delete the entire "working repo"
One big flaw I see in this is, I'm not sure how deletes would be tracked,
A key aspect is, the end result HAS to be REALLY easy to teach people to do
Thanks in advance,
Tom Malia
T <http://www.ttdsinc.com> &T Data Solutions L.L.C.
|
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.