Two experimental features: subrepos and shared repos

[Colin Caughie]

> What is the benefit of a shared repository?  This sounds similar to
> creating a local CVS repo and having everyone checkout their working
> directories from there.  I suppose you would get the benefit of
> atomic
> [sic?] changesets which CVS doesn't support but does it give you
> anything else?

I can see an immediate use for it when writing cross-platform code (which we do). I haven't tried it yet but I imagine our workflow could be something like this:

1. Clone a repo to my Linux home directory, with working directories on both Linux and Windows (using Samba sharing)
2. Get code working on Windows
3. Commit on Windows
4. Update on Linux
5. Get code working on Linux
6. Commit changes on Linux
7. Collapse the two commits if desired
8. Get code reviewed
9. Push

Assuming this would work it actually simplifies things a great deal. At the moment we use separate local repositories on Windows and Linux, pushing and pulling between the two as required. We do tend to collapse before getting code reviewed to simplify things for the reviewer, but that means that whichever repo we collapse in we have to judiciously strip the other to get it back in sync.

I look forward to trying this. Now I'm wondering if I could use a shared mq to avoid even the commit steps...

Colin


Latest News at: http://www.indigovision.com/news2009.php