Re: [fossil-users] Fossil for Android?

2014-07-14 Thread Oliver Friedrich
I think it is pretty dead. Maybe you can get the code from the owner by simply asking him? It served a whole directory, like fossil serve did. Am 14.07.2014 07:31, schrieb Urmil Parikh: Hi, I tried it today, but cannot get it to work. First, it told me that it could not find HOME folder

[fossil-users] 'syntax error in manifest' when checkin would result in empty worktree

2014-07-14 Thread Michai Ramakers
Hello, I guess this is a corner case - I was testing autosync here, and did basically the following (in short, making new repo, opening it, checking in new file, deleting this single file, and trying checkin again): $ mkdir f cd f $ fossil new f.f $ mkdir w w $ fossil open ../f.f $ touch a $

Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree

2014-07-14 Thread Jan Nijtmans
2014-07-14 11:07 GMT+02:00 Michai Ramakers m.ramak...@gmail.com: Hello, I guess this is a corner case - I was testing autosync here, and did basically the following (in short, making new repo, opening it, checking in new file, deleting this single file, and trying checkin again): $ mkdir f

Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree

2014-07-14 Thread Jan Nijtmans
2014-07-14 11:18 GMT+02:00 Jan Nijtmans jan.nijtm...@gmail.com: Easy to circumvent, so I think this is not urgent. I used a build from today's trunk. Thanks! I will have a look! I cannot reproduce it. The manifest of the initial non-empty check-in (containing 'a') looks like: C test

Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree

2014-07-14 Thread Michai Ramakers
On 14 July 2014 11:29, Jan Nijtmans jan.nijtm...@gmail.com wrote: 2014-07-14 11:18 GMT+02:00 Jan Nijtmans jan.nijtm...@gmail.com: I cannot reproduce it. The manifest of the initial non-empty check-in (containing 'a') looks like: C test D 2014-07-14T09:23:21.187 F a

Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree

2014-07-14 Thread Jan Nijtmans
2014-07-14 11:36 GMT+02:00 Michai Ramakers m.ramak...@gmail.com: Thanks for the very quick response. adding 'a': C added\sa D 2014-07-14T09:34:28.488 F a da39a3ee5e6b4b0d3255bfef95601890afd80709 P ac04821dcb98f1eda58cae5d83df619df110bdc5 U michai Z 66aec4a57515092f881cb0993a6d6f9f

Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree

2014-07-14 Thread Michai Ramakers
On 14 July 2014 11:38, Jan Nijtmans jan.nijtm...@gmail.com wrote: 2014-07-14 11:36 GMT+02:00 Michai Ramakers m.ramak...@gmail.com: Thanks for the very quick response. adding 'a': C added\sa D 2014-07-14T09:34:28.488 F a da39a3ee5e6b4b0d3255bfef95601890afd80709 P

Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree

2014-07-14 Thread Michai Ramakers
On 14 July 2014 11:43, Michai Ramakers m.ramak...@gmail.com wrote: On 14 July 2014 11:38, Jan Nijtmans jan.nijtm...@gmail.com wrote: 2014-07-14 11:36 GMT+02:00 Michai Ramakers m.ramak...@gmail.com: Thanks for the very quick response. adding 'a': C added\sa D 2014-07-14T09:34:28.488 F a

Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree

2014-07-14 Thread Jan Nijtmans
2014-07-14 11:48 GMT+02:00 Michai Ramakers m.ramak...@gmail.com: for completeness sake, that was fossil version 1.29 [9773eba5fe] 2014-06-11 00:51:07 UTC; upgrading to trunk on that host now. I can reproduce it now: If the manifest setting is on: $ fossil commit syntax error in manifest $ cat

Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree

2014-07-14 Thread Michai Ramakers
On 14 July 2014 12:53, Jan Nijtmans jan.nijtm...@gmail.com wrote: 2014-07-14 11:48 GMT+02:00 Michai Ramakers m.ramak...@gmail.com: for completeness sake, that was fossil version 1.29 [9773eba5fe] 2014-06-11 00:51:07 UTC; upgrading to trunk on that host now. I can reproduce it now: If the

Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree

2014-07-14 Thread Jan Nijtmans
2014-07-14 13:14 GMT+02:00 Michai Ramakers m.ramak...@gmail.com: On 14 July 2014 12:53, Jan Nijtmans jan.nijtm...@gmail.com wrote: I can reproduce it now: If the manifest setting is on: $ fossil commit syntax error in manifest Fixed here: www.fossil-scm.org/index.html/info/268ecf6ae9

Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree

2014-07-14 Thread Michai Ramakers
On 14 July 2014 13:38, Jan Nijtmans jan.nijtm...@gmail.com wrote: 2014-07-14 13:14 GMT+02:00 Michai Ramakers m.ramak...@gmail.com: On 14 July 2014 12:53, Jan Nijtmans jan.nijtm...@gmail.com wrote: I can reproduce it now: If the manifest setting is on: $ fossil commit syntax error in manifest

[fossil-users] purge/shun single branch(es)

2014-07-14 Thread Gour
Hello, the topic was already discussed several times in this mailing list, but I wonder what is the obstacle for Fossil to provide ability to shun/forge single branch(es), iow. whether it because it is, somehow, against Fossil's design or there are some implementation-wise reasons? I've started

[fossil-users] Minor fossil success story

2014-07-14 Thread Stephan Beal
Hi, all, Just moved today, don't have Internet except for my phone (as one can see by the autocompletion capitalizing Internet). There's barely enough signal to tether my pc with - cannot get a single web page to load. The only thing which works, in the sense of completing a network operation, is

Re: [fossil-users] purge/shun single branch(es)

2014-07-14 Thread Stephan Beal
0.02$ never really understood why people feel they need private branches. A little public humility once in a while helps make us better developers ☺ - stephan Sent from a mobile device, possibly from bed. Please excuse brevity and typos. On Jul 14, 2014 6:40 PM, Gour g...@atmarama.net wrote:

Re: [fossil-users] Minor fossil success story

2014-07-14 Thread Richard Hipp
Maybe I'll add Stephan's quote to http://www.fossil-svm.org/index.html/doc/tip/www/quotes.html -- D. Richard Hipp Sent from phone - Excuse brevity On Jul 14, 2014 8:05 PM, Stephan Beal sgb...@googlemail.com wrote: Hi, all, Just moved today, don't have Internet except for my phone (as one can

Re: [fossil-users] purge/shun single branch(es)

2014-07-14 Thread Gour
Stephan Beal sgb...@googlemail.com writes: 0.02$ never really understood why people feel they need private branches. A little public humility once in a while helps make us better developers First of all some code is simply too explorative by nature when one experiments with some new things

Re: [fossil-users] Minor fossil success story

2014-07-14 Thread Joe Prostko
On Mon, Jul 14, 2014 at 2:15 PM, Richard Hipp d...@sqlite.org wrote: Maybe I'll add Stephan's quote to http://www.fossil-svm.org/index.html/doc/tip/www/quotes.html I think you meant http://www.fossil-scm.org/index.html/doc/tip/www/quotes.wiki . :)

Re: [fossil-users] Minor fossil success story

2014-07-14 Thread Richard Hipp
On Mon, Jul 14, 2014 at 3:09 PM, Joe Prostko joe.pros...@gmail.com wrote: On Mon, Jul 14, 2014 at 2:15 PM, Richard Hipp d...@sqlite.org wrote: Maybe I'll add Stephan's quote to http://www.fossil-svm.org/index.html/doc/tip/www/quotes.html I think you meant

Re: [fossil-users] Minor fossil success story

2014-07-14 Thread Stephan Beal
Hold your finger down on a word until a selection pops up (assuming non-android works similarly). - stephan Sent from a mobile device, possibly from bed. Please excuse brevity and typos. On Jul 14, 2014 9:21 PM, Richard Hipp d...@sqlite.org wrote: On Mon, Jul 14, 2014 at 3:09 PM, Joe

Re: [fossil-users] purge/shun single branch(es)

2014-07-14 Thread Matt Welland
The desire for this ability, to sync or purge specific branches, has many possible motives - only one of which is hiding something :) Having the ability to push, remove and create private branches on a individual basis would make it much easier to use fossil for a gatekeeper based build system.

[fossil-users] CHANGED versus EDITED

2014-07-14 Thread Andy Goth
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When a file has been modified, [fossil diff -brief] reports it as CHANGED, whereas [fossil status] reports it as EDITED. Is this inconsistent terminology intentional? What other inconsistencies are possible between these two commands? I would have