On Mon, May 11, 2015 at 11:52 PM, Andy Goth <andrew.m.g...@gmail.com> wrote:
> On 5/11/2015 3:08 PM, Ron W wrote: > > Another possible work-around (besides what Andy and I suggested) would > > be for contributing devs to mark their trunks (and other designated > > "protected" branches) as private. > > I've considered this, but there are some considerable drawbacks. One, > the abandoned versions can be forever lost, even if they may have become > eventually useful for reference or future integration if requirements > change. Two, this restricts each developer to work from a single > repository file, so (depending on how things are set up) they may not be > able to access their code if their favorite shared terminal in the lab > is occupied one day. > Actually, a dev can do "fossil pull --private" to get all her/his changes from the shared PC. Also, Fossil repo files can live on file servers, so a dev could access her/his repos from any PC with access to the desired repo files. (Where I work, even though we each have assigned PCs, we also each have a "network home" directory where we can save files we might need to access when logged into a "lab PC")
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
