Hi, (Newbie alert! You've warned :) )
D. Richard Hipp wrote: > I'm looking to extend the command-line interface of fossil to handle > two new use cases. But I would like advice from the community on what > the user interface for these features should look like. If you have a > chance, please read over what I am trying to accomplish and suggest > ways of structuring the CLI interface. > > OVERVIEW > > In the current fossil design, an open check-out is only associated > with a single fossil repository. When you do "fossil open" that > creates your local check-out and associates it with one particular > local repository and no other. I would like to extend this to allow > an open check-out to be associated with two or more repositories. > > USE CASE 1: Private Branches > > Suppose there is a high-visibility public project bigproj.fossil. > Alice has a local clone of bigproj.fossil and has a local check-out of > the sources. She want's to contribute. But she always wants to > experiment privately before committing all of her changes for the > world to see. She would like a private branch. > > To do this, Alice runs a command > > ??What should this command be?? Using still one file for repository; since, Alice may need others work (even contibute to trunk) while working on private branch. Until she decide otherwise her private branch is hidden. fossil branch new BRANCH-NAME BASIS ?-bgcolor COLOR? ?-private? > > [snipped] > > Thanks for your attention. > > D. Richard Hipp > [email protected] > > _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
