On Tue, Dec 2, 2014 at 1:10 AM, Andy Bradford
wrote:
> Thus said Richard Hipp on Mon, 24 Nov 2014 07:35:55 -0500:
>
> > (1) Bundles. A bundle is a single file (another SQLite database, of
> > course) that encapsulates one or more check-ins. An unprivileged user
> > can clone a repo and make
Thus said Richard Hipp on Mon, 24 Nov 2014 07:35:55 -0500:
> (1) Bundles. A bundle is a single file (another SQLite database, of
> course) that encapsulates one or more check-ins. An unprivileged user
> can clone a repo and make their own local changes, then package those
> changes into a bu
On Mon, Nov 24, 2014 at 6:16 PM, Stephan Beal wrote:
> Do they have one big shared branch or does each have his own? If the
> latter, how do we differentiate the N anonymous users? Maybe give each one
> a token (a UUID) unique to his branch? He can share that token with others
> to allow pushing
On Mon, Nov 24, 2014 at 1:35 PM, Richard Hipp wrote:
> Among the enhancements I mgiht experiment with this week (assuming I am
> not pulled off to work on SQLite problems that pop up unexpectedly) are the
> following:
>
And here i always thought all problems in sqlite are unexpected!
> (1) Bun
I'm getting increasing pressure to provide Fossil with "drive-by-patch
workflow" capabilities. By this I mean capabilities that make it easier
for random passers-by on the internet to contribute changes to a project.
GitHub provides that capability using pull-requests, for example.
I've started a
