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. > > Then, when working on a feature/fix branch, "fossil publish branchname" > to make that branch push-able.
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. That's right, it's not always possible for people to have their own computers at their own desks. I often deal with development on a segregated network, and within that segregated network people are not assigned individual computers. -- Andy Goth | <andrew.m.goth/at/gmail/dot/com>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
