[fossil-users] Ignore directories
How can I make `fossil extra` and `fossil addremove` ignore whole directories? -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Congrats to GitHub
GitHub got $100 million in venture capital from Andreessen Horowitz, according to press reports. http://online.wsj.com/article/SB10001424052702303292204577517111643094308.html Marc Andreessen, you may recall, is the Mosaic/Netscape guy. Here's hoping that GitHub will use their new cash infusion to steal some of the ideas and code from Fossil in order to fix a few of the more serious shortcomings of git. :-) I wish them all the best. If anybody on this list has any contacts at GitHub, I really do want them to steal Fossil ideas in order to improve Git, and would like to give them a presentation on ideas of how they might go about that. Please put us in touch. Tnx. -- 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] Ignore directories
put “path/to/dir/*” into the “ignore-glob” setting. The most simple is to add that line to the file “.fossil-settings/ignore-glob” and to start versioning that file. Otherwise consult “fossil help settings”. 2012/7/10 Baruch Burstein bmburst...@gmail.com: How can I make `fossil extra` and `fossil addremove` ignore whole directories? -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Benoit Mortgat ___ 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] anything speaking against fossil add --commit ?
On 07/10/12 10:30, Benoit Mortgat wrote: What do you want the command to do in this case: * edit foo.txt (versioned) * fossil add --commit bar.txt Do you want the commit to just add bar.txt to the version control, or to also include foo.txt changes? Given that fossil add is a no-op when a file is versioned already, it would be natural to just do what has been asked: add and commit, i.e., no-op and commit. Regards, -Martin ___ 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] anything speaking against fossil add --commit ?
On Mon, Jul 9, 2012 at 11:15 AM, Weber, Martin S martin.we...@nist.govwrote: Often I will run the following two commands: fossil add list of files ^add^ci (i.e., fossil ci list of files) immediately afterwards. Sometimes I forget the second step and then do some funny stuff (changing trunks, merging etc.) until I stumble over the uncommitted files. Is there anything speaking against adding a --commit (and maybe --message) option to add so that it'll commit immediately? Why do you think you will be more likely to type --commit after fossil add than you would be to type ; fossil commit? -Martin ___ 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] anything speaking against fossil add --commit ?
On 07/10/12 12:13, Richard Hipp wrote: Why do you think you will be more likely to type --commit after fossil add than you would be to type ; fossil commit? Well, assuming there's a shorthand for the option, I find it more natural to add these extra three characters on the 'add' line than going CTRL+P CTRL+A ALT+f ALT+f CTRL+w ci (or ^add^ci). Usually I don't want to commit freshly added files and changed, versioned files in one go. Often enough though, I do have additions and commits at the same time :) In the seldom cases where I'm just adding something, I'm usually lazy and go addremove;ci which is short enough because there's no list of filenames involved. I'd of suggested add commits automatically (or setting-based), but figured I wouldn't get very far with that.. So in the end, say, fossil add -c, is just a (personally perceived) usability improvement on the CLI. Regards, -Martin ___ 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] Still ask for password with ssh protocol
On Mon, Jul 9, 2012 at 5:43 PM, Martin Gagnon eme...@gmail.com wrote: Hi list.. When I use ssh:// protocol on remote-url and I specify my usename in it: e.g.: ssh://user@host/path/to/repo.fossil Fossil prompt me for a password, I can enter anything and it work. I know that recently, authentication got bypassed when using ssh protocol, but it seems that the password prompt when specifying password in the remote-url is still present while useless in ssh mode. I guess the prompt should be remove when using ssh://. Note: it's not ssh itself asking me for password, I use keys, it's really fossil. Here a patch I propose, I tried to use the url_get_password_if_needed function for that case, but there was some duplicated conditions check and I didn't want to re-order too much the code.. So I just add a simple condition check in the proper place. Regards -- Martin G. ssh_noprompt.patch Description: Binary data ___ 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] Markdown engine integrated into fossil
On 2012-07-09 15:41, Richard Hipp wrote: On Mon, Jul 9, 2012 at 3:31 AM, Baptiste Daroussin baptiste.darous...@gmail.com [6] wrote: 2012/6/7 Richard Hipp d...@sqlite.org [1]: My priority is to get WYSIWYG wiki editing going, at which point the underlying wiki formatting language becomes largely irrelevant, no? Far from criticising your decision to write such an editor, I offer the observation that If a markdown jquery editor would be used, then the available markdown library could be used for rendering, jquery for client side Since we are using it anyway. Those wysiwyg markdown editors are available and leave us only with interfacing/integration. The maintenance burden on the editor is not with us And, maybe, we can offer a migration path for existing wiki and/or embedded documentation? D. Richard Hipp d...@sqlite.org [5] -- Rene ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
