Re: [fossil-users] Fossil for Android?
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 (which was null). After explicitely editing HOME, it says it cannot open database. Is this app maintained? Does it support serving a single repo or multiple ones (like fossil serve folder)? Thanks - Urmil On Mon, Jun 16, 2014 at 8:25 PM, Oliver Friedrich beowul...@gmx.de mailto:beowul...@gmx.de wrote: Hi Urmil, actually there is an apk for fossil, though it only supports serving repos AFAIR. https://play.google.com/store/apps/details?id=es.dadbiz.fossil I used it often to backup my repos to my phones sd-card and it worked out quite well. Am 16.06.2014 12:02, schrieb Urmil Parikh: There was some discussion in past about compiling fossil for Android. Is it still alive? Is there any .apk available? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org mailto:fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] 'syntax error in manifest' when checkin would result in empty worktree
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 $ fossil addremove $ fossil ci -m 'added a' $ rm a $ fossil addremove $ fossil ci -m 'deleted a' syntax error in manifest Easy to circumvent, so I think this is not urgent. I used a build from today's trunk. Michai ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree
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 cd f $ fossil new f.f $ mkdir w w $ fossil open ../f.f $ touch a $ fossil addremove $ fossil ci -m 'added a' $ rm a $ fossil addremove $ fossil ci -m 'deleted a' syntax error in manifest Easy to circumvent, so I think this is not urgent. I used a build from today's trunk. Thanks! I will have a look! Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree
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 D 2014-07-14T09:23:21.187 F a da39a3ee5e6b4b0d3255bfef95601890afd80709 R cc0f80fb4844083b912f66e9f12acc1c T *branch * trunk T *sym-trunk * U nijtmaj Z 05abe02960a6a7b437f5ab423f8660c4 The manifest of the second check-in looks like: C test\s2 D 2014-07-14T09:23:42.974 P a98d6afd09cf5aa06159d771d58327b5745f5a74 R d41d8cd98f00b204e9800998ecf8427e U nijtmaj Z 547b7af754541933479851726c1b2e92 Fossil doesn't report a syntax error, neither do I see one. How does the manifest of the your first check-in look like? Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree
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 da39a3ee5e6b4b0d3255bfef95601890afd80709 R cc0f80fb4844083b912f66e9f12acc1c T *branch * trunk T *sym-trunk * U nijtmaj Z 05abe02960a6a7b437f5ab423f8660c4 The manifest of the second check-in looks like: C test\s2 D 2014-07-14T09:23:42.974 P a98d6afd09cf5aa06159d771d58327b5745f5a74 R d41d8cd98f00b204e9800998ecf8427e U nijtmaj Z 547b7af754541933479851726c1b2e92 Fossil doesn't report a syntax error, neither do I see one. How does the manifest of the your first check-in look like? 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 (BTW, I recreated a repo and set 'manifest on' - how to display a manifest for a checkin..?) Michai ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree
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 (BTW, I recreated a repo and set 'manifest on' - how to display a manifest for a checkin..?) So, the T-cards are missing from the initial check-in.. why Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree
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 ac04821dcb98f1eda58cae5d83df619df110bdc5 U michai Z 66aec4a57515092f881cb0993a6d6f9f (BTW, I recreated a repo and set 'manifest on' - how to display a manifest for a checkin..?) So, the T-cards are missing from the initial check-in.. why Aargh, my mistake (about the T-cards that is) - using an older fossil version on another host. Xterms look so alike... With today's trunk build then, adding 'a': C added\sa D 2014-07-14T09:40:55.081 F a da39a3ee5e6b4b0d3255bfef95601890afd80709 R cc0f80fb4844083b912f66e9f12acc1c T *branch * trunk T *sym-trunk * U michai Z 7a54f9b1f233b82116c75ebd1a9cd75f The error is still there when fossil-deleting 'a', then trying checkin. This is fossil version 1.30 [ec2061ce02] 2014-07-14 07:22:40 UTC Michai ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree
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 da39a3ee5e6b4b0d3255bfef95601890afd80709 P ac04821dcb98f1eda58cae5d83df619df110bdc5 U michai Z 66aec4a57515092f881cb0993a6d6f9f (BTW, I recreated a repo and set 'manifest on' - how to display a manifest for a checkin..?) So, the T-cards are missing from the initial check-in.. why Aargh, my mistake (about the T-cards that is) - using an older fossil version on another host. for completeness sake, that was fossil version 1.29 [9773eba5fe] 2014-06-11 00:51:07 UTC; upgrading to trunk on that host now. Michai ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree
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 manifest C test2 D 2014-07-14T09:48:52.610 P b2b00905588b87dfb6b916e420c2d18ae290eb15 U nijtmaj Z 811e82701ab5ba78994bcaa69348fad8 $fossil update .. $ cat manifest C test D 2014-07-14T09:48:15.229 F a da39a3ee5e6b4b0d3255bfef95601890afd80709 R cc0f80fb4844083b912f66e9f12acc1c T *branch * trunk T *sym-trunk * U nijtmaj Z 99f2b07b52481e5b63556c50fe8bf2ad investigating further. Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree
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 manifest setting is on: $ fossil commit syntax error in manifest $ cat manifest C test2 D 2014-07-14T09:48:52.610 P b2b00905588b87dfb6b916e420c2d18ae290eb15 U nijtmaj Z 811e82701ab5ba78994bcaa69348fad8 $fossil update .. $ cat manifest C test D 2014-07-14T09:48:15.229 F a da39a3ee5e6b4b0d3255bfef95601890afd80709 R cc0f80fb4844083b912f66e9f12acc1c T *branch * trunk T *sym-trunk * U nijtmaj Z 99f2b07b52481e5b63556c50fe8bf2ad Ok. For pinpointing, note that this reproduces here without the 'old' fossil being involved in any way. (But if T-cards should have been present there, that may be another bug perhaps - I know next to nothing about cards.) I've pasted a script(1) session of what happens here using today's trunk build: --- /tmp$ f ver This is fossil version 1.30 [ec2061ce02] 2014-07-14 07:22:40 UTC /tmp$ mkdir f cd f /tmp/f$ f new f.f project-id: 1b75b2a4e801b2853818bc8452f4af71718f9965 server-id: 9194bf54837bbb1539bd6945381f874bb3bbbeac admin-user: michai (initial password is d95df6) /tmp/f$ mkdir w cd w /tmp/f/w$ f open ../f.f project-name: unnamed repository: /tmp/f/w/../f.f local-root: /tmp/f/w/ config-db:/home/michai/.fossil project-code: 1b75b2a4e801b2853818bc8452f4af71718f9965 checkins: 0 /tmp/f/w$ f set manifest on /tmp/f/w$ f set | grep mani manifest (local) on /tmp/f/w$ touch a /tmp/f/w$ f addr ADDED a added 1 files, deleted 0 files /tmp/f/w$ f ci -m 'added a' New_Version: dcf0afee44daa83f3c47883a7d37631b96b7f57d /tmp/f/w$ cat manifest C added\sa D 2014-07-14T11:04:48.671 F a da39a3ee5e6b4b0d3255bfef95601890afd80709 R cc0f80fb4844083b912f66e9f12acc1c T *branch * trunk T *sym-trunk * U michai Z 01b31663e07cf39a347f53c7b0d355a9 /tmp/f/w$ rm a /tmp/f/w$ f addr DELETED a added 0 files, deleted 1 files /tmp/f/w$ f ci -m 'deleted a' syntax error in manifest /tmp/f/w$ --- Michai ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree
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 The problem was not in the T-card, it was the R-card. And it was not the manifest setting exposing the problem, it was the repo-cksum setting. Although the generated manifest was perfectly valid, it was mistaken for an invalid Control manifest, which cannot have a P-card. Corrected now. Thanks for the report! Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] 'syntax error in manifest' when checkin would result in empty worktree
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 Fixed here: www.fossil-scm.org/index.html/info/268ecf6ae9 The problem was not in the T-card, it was the R-card. And it was not the manifest setting exposing the problem, it was the repo-cksum setting. Although the generated manifest was perfectly valid, it was mistaken for an invalid Control manifest, which cannot have a P-card. Corrected now. works very well - thanks for the quick fix. Michai ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] purge/shun single branch(es)
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 my exploration of DVCS terrain with darcs many years ago and tried (almost) all DVCS-es (darcs, bazaar, hg, mtn, git, fossil) and lastly (mostly) using Git liking its light-branching features. Fossil is also very light when it comes to branching, so I'd like to take advantage of its private branches - sometimes there is simply useful to experiment with some work in private and then merge and/or dispose later, but the current feature allows only to remove all private branches from a repository... with the fossil scrub --private, but, imho, ability to purge single branch from the repo would make the branching mechanism even more smooth. Any thought? Sincerely, Gour -- As a blazing fire turns firewood to ashes, O Arjuna, so does the fire of knowledge burn to ashes all reactions to material activities. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Minor fossil success story
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 fossil! - stephan Sent from a mobile device, possibly from bed. Please excuse brevity and typos. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] purge/shun single branch(es)
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: 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 my exploration of DVCS terrain with darcs many years ago and tried (almost) all DVCS-es (darcs, bazaar, hg, mtn, git, fossil) and lastly (mostly) using Git liking its light-branching features. Fossil is also very light when it comes to branching, so I'd like to take advantage of its private branches - sometimes there is simply useful to experiment with some work in private and then merge and/or dispose later, but the current feature allows only to remove all private branches from a repository... with the fossil scrub --private, but, imho, ability to purge single branch from the repo would make the branching mechanism even more smooth. Any thought? Sincerely, Gour -- As a blazing fire turns firewood to ashes, O Arjuna, so does the fire of knowledge burn to ashes all reactions to material activities. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Minor fossil success story
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 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 fossil! - stephan Sent from a mobile device, possibly from bed. Please excuse brevity and typos. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] purge/shun single branch(es)
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 and it might not bring much value to the whole project, so why should one keep it around? Second, DVCS are used for non-coding projects as well - e.g, writing - where rewriting is very common thing where things are very often simply discarded, so I do not see why not being able to simply trash it? In other DVCS-es like Git it's very easy to create/dispose branches, so there is, naturally no need for private branches. Iow, in my use-case it's not at all about possible public humiliation - if there won't be private branches in Fossil, one could simply create separate Fossil repo, explore new ideas and then simply integrate it into 'official' repo, so the issue is to dispose something one does not want/need to keep around (almost) forever;) Sincerely, Gour -- As the ignorant perform their duties with attachment to results, the learned may similarly act, but without attachment, for the sake of leading people on the right path. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Minor fossil success story
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 . :) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Minor fossil success story
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 http://www.fossil-scm.org/index.html/doc/tip/www/quotes.wiki . :) Thanks. That's what happens when I try to type on a phone. I still haven't figured out how to cut-and-paste ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Minor fossil success story
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 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 http://www.fossil-scm.org/index.html/doc/tip/www/quotes.wiki . :) Thanks. That's what happens when I try to type on a phone. I still haven't figured out how to cut-and-paste ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] purge/shun single branch(es)
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. This is something I'd like to see. The original request was for normal branches. Being able to purge a single private branch would be sufficient I think. I like this idea better than the idea of syncing/purging normal branches as the fossil philosophy of convergence on a single data view in all instances has proven to be an important feature. On Mon, Jul 14, 2014 at 11:07 AM, Stephan Beal sgb...@googlemail.com wrote: 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: 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 my exploration of DVCS terrain with darcs many years ago and tried (almost) all DVCS-es (darcs, bazaar, hg, mtn, git, fossil) and lastly (mostly) using Git liking its light-branching features. Fossil is also very light when it comes to branching, so I'd like to take advantage of its private branches - sometimes there is simply useful to experiment with some work in private and then merge and/or dispose later, but the current feature allows only to remove all private branches from a repository... with the fossil scrub --private, but, imho, ability to purge single branch from the repo would make the branching mechanism even more smooth. Any thought? Sincerely, Gour -- As a blazing fire turns firewood to ashes, O Arjuna, so does the fire of knowledge burn to ashes all reactions to material activities. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Matt -=- 90% of the nations wealth is held by 2% of the people. Bummer to be in the majority... ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] CHANGED versus EDITED
-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 thought they'd share the same reporting code. - -- Andy Goth | andrew.m.goth/at/gmail/dot/com -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTxJf3AAoJELtYwrrr47Y4ZEEH/3liMbB50goRpnrVTHsRbGc1 oYTHsqDz+n9Ipd9a7yloLvKk4dljkFFeZ38EjgMOCC6MXLFQUjsgLQi7A0CYjuuP Fzd0NB0a/LrK2CHyLlGEvUozL5IRH4h/gGkNqNPG2/ZETPLsDEhHnl5HA9xnhGSq 2AUmeSvIZKYQ1rk/lAbUCP7QGWfTSQIY34+sJvFo8eqsxPhnGWgAQESmT7iti/Cn qQyGSVe0dxn+Q5Q729RqbhkPyciPQo6+ZZiyIrxsDCD5Y12tdqe9w+/VqIGWcFlI hUYaIfkQ+U6sK6A71hieL+5uMLSP5jV3ZaFEH/Z8zmrTiC0fbGjeTKBSzsnzSBE= =nNVq -END PGP SIGNATURE- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
