Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Gerhard Fiedler wrote: >> If you create a "PUBLIC" branch from HEAD (where you have the open >> code), then set permissions on trunk and branch such that the >> anonymous users are only able to check out the branch whereas your >> developers can check out everything then it might work. > > Another option might be to create a repository for public use, and > whenever you consider the code stable, you transfer whatever is in > your private repository to the public repository. This can be done > pretty much automatically by a script. > > Alternatively, you can probably create a commitinfo script that does > this double commit on every commit, if complete up-to-date-ness is > desired for the public code. > > In any case, there will be some work that has to be done even if you > use only one repository and a PUBLIC branch. In this case you need to > merge or copy the changes to the branch. I think this is not less > work than working with different repositories, and the configuration > is more flexible with different repositories. Thanks for the ideas! I'll need to check out what might be suitable here... Koen