- Original Message -
From: "D. Richard Hipp"
To: fossil-users
Subject: [fossil-users] User interface design questions
Date: Mon, 26 Jan 2009 10:21:27 -0500
[snip]
>USE CASE 1: Private Branches
I'd do this by-hand by
1. Copying the checkout, (or some version of
I like the new branching changes, they fit in very nicely (with my view of
the subject :-) , but also into the internal workings of fossil with
surprisingly little disruption).
Anyway, here are my thoughts on the next bit...
> I'm looking to extend the command-line interface of fossil to handle t
On Tue, Jan 27, 2009 at 12:41 PM, Dan wrote:
> suggest any concrete examples.. perhaps it would be easier to keep it all in
> the
> same repository, but force certain branches to require extra permissions??? so
> public checkins could be kept in a '-public' branch, and only certain users
> could
I see UseCase1 as a private branch in a local clone of an existing repository.
The ability to only 'sync' the last in a series of commits back to the 'master'
repository would be good.. perhaps by extending the new branch functionality to
be able to flag a particular branch as --private ??? (and
Hi Richard,
On Mon, 26 Jan 2009 10:21:27 -0500, you wrote:
[nice proze]
>USE CASE 1: Private Branches
>
>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, Ali
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, ple
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 stru
7 matches
Mail list logo
