Re: [fossil-users] JavaScript error in div class=content
Am 25.02.2015 19:01 schrieb Richard Hipp d...@sqlite.org: What am I overlooking? Sorry my fault, the script code is correct. ___ 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] select menus and back button
On Wed, Feb 25, 2015 at 9:14 PM, Richard Hipp d...@sqlite.org wrote: On 2/25/15, Ron W ronw.m...@gmail.com wrote: As best I can recall, this is the same behavior I've seen with many other web apps, including a few I worked on. My work around for this was to include a Javascript function, triggered by the onload event, to reset selection menus to the options that match the page content. I don't think the Back button triggers onload. At least it didn't in the experiment I tried a few minutes ago... It's been many years and I no longer have that code, so I can't look at what I did. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Spelling corrections for fossil-scm.org
Hello All, I found the following spelling mistakes on the website. The misspelled word begins and ends in *. I don't know the difference between descendants vs. descendents http://www.fossil-scm.org/index.html/doc/trunk/www/faq.wiki You can also add (and remove) tags from a check-in using the web interface. First locate the check-in that you what to tag on the *tmline* All *descendents* of a private check-in are also private. First locate the check-in that you what to tag on the *tmline*, then click on the link to go the detailed information page for that check-in. http://www.fossil-scm.org/index.html/doc/trunk/www/quickstart.wiki The URL above is the http URL for the fossil repository you want to clone, http://www.fossil-scm.org/index.html/doc/trunk/www/fileformat.wiki descendants (but not *descendents* through a merge) http://www.fossil-scm.org/index.html/doc/trunk/www/stats.wiki The number of bytes sent from client to server is *neglible* in comparison. Analysis And *Supplimental* Data http://www.fossil-scm.org/index.html/doc/trunk/www/server.wiki Fossil can be run directly from stunnel in a *mannar* similar to inetd and xinetd. *expecially* on repositories with a large number of files or with long revision histories. http://www.fossil-scm.org/index.html/doc/trunk/www/checkin_names.wiki Usually *whan* a branch name is specified, it means the latest checkin on that branch. For example, the command fossil purge XYZ means to purge the checkin XYZ and all of its *descendents.* http://www.fossil-scm.org/index.html/doc/trunk/www/inout.wiki VCS interchange formats, and so for compatibility, the use of the --git option *recommented.* http://www.fossil-scm.org/index.html/doc/trunk/www/fossil-v-git.wiki branches that they want to share and keep other *branchs* of the project private. Fossil views history as sacrosanct and *stubbornly* refuses to change it. http://www.fossil-scm.org/index.html/doc/trunk/www/fiveminutes.wiki Remove files that haven't been *commited* yet This shows the list of changes that have been done and will be *commited* the next time you run fossil commit. fossil finfo myfile: Note the first hash, which is the UUID of the commit when the file was *commited* http://www.fossil-scm.org/index.html/doc/trunk/www/contribute.wiki we will be forced to *reimplement* your changes from scratch which might http://www.fossil-scm.org/index.html/doc/trunk/www/copyright-release.html that is *mananged* by Hipp, Wyrick Company, Inc. You are authorized to sign this agreement on behalf of your company (if *applicable*). no titlie on this page http://www.fossil-scm.org/index.html/doc/trunk/www/private.wiki For example, you might be building a cross-platform application and have separate repositories on your *windows* laptop, your *linux* desktop, and your iMac. http://www.fossil-scm.org/index.html/doc/trunk/www/changes.wiki Improvements to the ssh:// sync protocol, to help it move past *noisey* When used, the mtime of all *mananged* files is set to the time when the most recent version of the file was checked in. Changed the vdiff webpage to show the complete text of files that were added or removed (the *equivalent* of using the -N or --newfile options with the fossil diff command-line.) Background colors for branches are *choosen* automatically if no color is specified by the user. http://www.fossil-scm.org/index.html/doc/trunk/www/style.wiki list starts at # 10? http://www.fossil-scm.org/index.html/doc/trunk/www/delta_format.wiki *Ckecksum* http://www.fossil-scm.org/index.html/doc/trunk/www/quotes.wiki Git approaches the *useability* of iptables, which is to say, utterly unusable unless you have the manpage tattooed on you arm. http://www.fossil-scm.org/index.html/doc/trunk/www/th1.md The original TCL language after when TH1 is modeled has a very rich *repertoire* of commands. http://www.fossil-scm.org/index.html/doc/trunk/www/webui.wiki You can view summary reports of branches in the check-in graph by visiting the *Branche* links on the menu bar. http://www.fossil-scm.org/index.html/wiki?name=Auto-completion MS At least on my system (*ubuntu*) many programs -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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] Spelling corrections for fossil-scm.org
On 26 February 2015 at 18:19, jungle Boogie jungleboog...@gmail.com wrote: I found the following spelling mistakes on the website. The misspelled word begins and ends in *. thank you; I can fix this in a few hours from now, unless anyone else is eager to do so earlier. 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] Tags and unhide
On Thu, Feb 26, 2015 at 3:12 AM, Gaurav M. Bhandarkar gaurav.a...@gmail.com wrote: OK. The idea that comment on a version is also a tag is new to me. IMO, this fossil specific tag definition caused this query. When we say Tags in context of a SCM, people usually think of a label which wraps around a specific version of file(s). Tags in Fossil have a more expansive definition. The side effect being that features like Recent Tags show more than expected. But, technically, a comment is a verbose label wrapped around a commit. I think you guys could just display something like https://www.fossil-scm.org/fossil/tagtimeline instead of what we are displaying now for tags. That is less cluttered by not showing individual comment updates. Maybe the tags option should be renamed tag updates. I'm not sure what the best name for this tagtimeline view would be. tags is not what I would call it. That doesn't convey (to me) how it is different from check-ins. (And check-ins-only-non-propagating is way too long.) ___ 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] Spelling corrections for fossil-scm.org
Hi Brad, On 26 February 2015 at 09:57, bch brad.har...@gmail.com wrote: Could you supply these as a diff? Anybody with a local copy can edit the files in question and, if not commit-and-publish (because of permissions), supply a standard, machine handlable format, versus an ad hoc, error-prone, and (I suspect) time-consuming-to-produce format. Thanks for reviewing all this and identifying problems!!! Yes, I can supply a diff. It will take a few hours but I'd rather do it correctly. Do we want to always use check-in or checkin? The former is more common but the timeline page lists 'checkins'. These are corrections of spelling mistakes and after all these are corrected, I'll review possible double words and grammar issues. Best, jungle -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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] Spelling corrections for fossil-scm.org
On 26 February 2015 at 18:19, jungle Boogie jungleboog...@gmail.com wrote: I found the following spelling mistakes on the website. The misspelled word begins and ends in *. ... Please verify that http://fossil-scm.org/index.html/info/05fc09c5ddc1b00f is what you meant. Not changed (yet): http://www.fossil-scm.org/index.html/doc/trunk/www/quickstart.wiki The URL above is the http URL for the fossil repository you want to clone, What did you mean? (Alternatively, please post a diff.) http://www.fossil-scm.org/index.html/doc/trunk/www/contribute.wiki we will be forced to *reimplement* your changes from scratch which might 'Reimplement' is correct, I think - what did you mean? http://www.fossil-scm.org/index.html/doc/trunk/www/copyright-release.html ... no titlie on this page Didn't add a title yet. http://www.fossil-scm.org/index.html/doc/trunk/www/style.wiki list starts at # 10? I guess it's basically 'section * 10 + item_index' :-) http://www.fossil-scm.org/index.html/wiki?name=Auto-completion MS At least on my system (*ubuntu*) many programs michai@delle:/tmp/f/f/www$ grep -ir ubuntu * michai@delle:/tmp/f/f/www$ What did you mean? (Or please post a diff.) Thx again, 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] Spelling corrections for fossil-scm.org
checkins reminds me of chickens, for what it's worth. If we at least standardize on one, a global search/replace to update them becomes much more possible. -bch On 2/26/15, jungle Boogie jungleboog...@gmail.com wrote: Hi Brad, On 26 February 2015 at 09:57, bch brad.har...@gmail.com wrote: Could you supply these as a diff? Anybody with a local copy can edit the files in question and, if not commit-and-publish (because of permissions), supply a standard, machine handlable format, versus an ad hoc, error-prone, and (I suspect) time-consuming-to-produce format. Thanks for reviewing all this and identifying problems!!! Yes, I can supply a diff. It will take a few hours but I'd rather do it correctly. Do we want to always use check-in or checkin? The former is more common but the timeline page lists 'checkins'. These are corrections of spelling mistakes and after all these are corrected, I'll review possible double words and grammar issues. Best, jungle -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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] Spelling corrections for fossil-scm.org
Hi Brad, On 26 February 2015 at 10:40, bch brad.har...@gmail.com wrote: checkins reminds me of chickens, for what it's worth. If we at least standardize on one, a global search/replace to update them becomes much more possible. I agree--on both accounts! -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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] Spelling corrections for fossil-scm.org
jungle Boogie wrote: Hello All, I found the following spelling mistakes on the website. The misspelled word begins and ends in *. I don't know the difference between descendants vs. descendents Both are correct. Descendant seems to be more common than descendent, but it can be argued that the latter is more correct based on the Latin etymon (descendens, pres. part. of the 3rd conjugation verb descendere). (Pedantic, I know.) -- Will ___ 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] Spelling corrections for fossil-scm.org
(Pedantic, I know.) +1 On 2/26/15, Will Parsons varro@nodomain.invalid wrote: jungle Boogie wrote: Hello All, I found the following spelling mistakes on the website. The misspelled word begins and ends in *. I don't know the difference between descendants vs. descendents Both are correct. Descendant seems to be more common than descendent, but it can be argued that the latter is more correct based on the Latin etymon (descendens, pres. part. of the 3rd conjugation verb descendere). (Pedantic, I know.) -- Will ___ 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] Spelling corrections for fossil-scm.org
Hi Michai,
On 26 February 2015 at 12:30, Michai Ramakers m.ramak...@gmail.com wrote:
On 26 February 2015 at 18:19, jungle Boogie jungleboog...@gmail.com wrote:
I found the following spelling mistakes on the website. The misspelled
word begins and ends in *.
...
Please verify that
http://fossil-scm.org/index.html/info/05fc09c5ddc1b00f is what you
meant.
Not changed (yet):
I just finished my diffs (recommended by Brad) and I've attached.
I'll looks yours over, too, but my diffs contain some grammar corrections.
Thx again,
Michai
Thank YOU,
jungle
--
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
--- www/copyright-release.html
+++ www/copyright-release.html
@@ -3,11 +3,11 @@
This agreement applies to your contribution of material to the
Fossil Software Configuration Management System ("Fossil") that is
-mananged by Hipp, Wyrick Company, Inc. ("Hwaci") and
+managed by Hipp, Wyrick Company, Inc. ("Hwaci") and
sets out the intellectual property rights you grant to Hwaci in the
contributed material.
The terms "contribution" and "contributed material" mean any source code,
object code, patch, tool, sample, graphic, specification, manual,
documentation, or any other material posted, submitted, or uploaded by
@@ -66,11 +66,11 @@
grant the rights set out in this agreement.
Your contribution does not, to the best of your knowledge and belief,
violate any third party's copyrights, trademarks, patents,
or other intellectual property rights.
You are authorized to sign this agreement on behalf of your
- company (if appliable).
+ company (if applicable).
By filling in the following information and signing your name,
you agree to be bound by all of the terms
changes.wiki
Description: Binary data
checkin_names.wiki
Description: Binary data
contribute.wiki
Description: Binary data
delta_format.wiki
Description: Binary data
faq.wiki
Description: Binary data
fileformat.wiki
Description: Binary data
fiveminutes.wiki
Description: Binary data
fossil-v-git.wiki
Description: Binary data
inout.wiki
Description: Binary data
private.wiki
Description: Binary data
quickstart.wiki
Description: Binary data
server.wiki
Description: Binary data
stats.wiki
Description: Binary data
th1.md
Description: Binary data
webui.wiki
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] Spelling corrections for fossil-scm.org
Hi Michai, On 26 February 2015 at 12:30, Michai Ramakers m.ramak...@gmail.com wrote: On 26 February 2015 at 18:19, jungle Boogie jungleboog...@gmail.com wrote: I found the following spelling mistakes on the website. The misspelled word begins and ends in *. ... Please verify that http://fossil-scm.org/index.html/info/05fc09c5ddc1b00f is what you meant. Not changed (yet): Your changes look good and my diffs should answer any questions you have. I didn't modify the quotes one after all as someone misspelled but perhaps we could have the correct spelling in parentheses. Git approaches the useability (usability) of iptables, which is to say, utterly Or keep your changes. What did you mean? (Or please post a diff.) Thx again, Michai -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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] Spelling corrections for fossil-scm.org
On 26 February 2015 at 21:50, jungle Boogie jungleboog...@gmail.com wrote: Your changes look good and my diffs should answer any questions you have. I didn't modify the quotes one after all as someone misspelled but perhaps we could have the correct spelling in parentheses. Git approaches the useability (usability) of iptables, which is to say, utterly Or keep your changes. indeed, the question of whether not to include quotes verbatim. I couldn't find the original one (on google) quickly enough, then figured it was not a legal document or anything, and so I corrected it. I'll look at your diffs now and fix any remainders accordingly. 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] Spelling corrections for fossil-scm.org
Hi Michai, On 26 February 2015 at 12:54, Michai Ramakers m.ramak...@gmail.com wrote: I'll look at your diffs now and fix any remainders accordingly. Great! There's 51 places where 'checkin' currently (trunk) occur. I'll work on diffs for those to make it check-in/s. Unless anyone likes to have checkin/s check-in/s in the documents. -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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] Spelling corrections for fossil-scm.org
On 26 February 2015 at 22:02, jungle Boogie jungleboog...@gmail.com wrote: There's 51 places where 'checkin' currently (trunk) occur. I'll work on diffs for those to make it check-in/s. Unless anyone likes to have checkin/s check-in/s in the documents. no need for diffs here - this is very simple to grep for. 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] Tags and unhide
OK. The idea that comment on a version is also a tag is new to me. IMO, this fossil specific tag definition caused this query. When we say Tags in context of a SCM, people usually think of a label which wraps around a specific version of file(s). I think you guys could just display something like https://www.fossil-scm.org/fossil/tagtimeline instead of what we are displaying now for tags. Thanks for explaining. -Gaurav On Thu, Feb 26, 2015 at 12:48 AM, Ron W ronw.m...@gmail.com wrote: On Wed, Feb 25, 2015 at 3:37 AM, Gaurav M. Bhandarkar gaurav.a...@gmail.com wrote: How is the output lines, eg 16:06 Edit [72114148]: Edit check-in comment. (user: drh) [details], related to most recent tags. For a check-in (or a ticket), comment is a tag. The comment tag also has a value, which is the test of the comment. (Beside being symbolic names, tags may also have values.) ___ 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] JavaScript error in div class=content
2015-02-25 19:01 GMT+01:00 Richard Hipp d...@sqlite.org:
On 2/25/15, Kai Lauterbach kla...@web.de wrote:
During this work I got serious error messages in my browser console:
Uncaught SyntaxError: Unexpected token }
function gebi(x){
^- Opening curly brace
if(/^#/.test(x)) x = x.substr(1);
In the previous line, a regular expression is used, which is
only available in javascript 5.1 and higher. My guess is
that your browser uses a javascript version older than that.
var e = document.getElementById(x);
if(!e) throw new Error(Expecting element with ID +x);
else return e;}
^- Close curly brace
/script
What am I overlooking?
Possible workaround (which is hardly more complicated) here:
http://fossil-scm.org/index.html/info/e7ec49815b988811
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
[fossil-users] Prevent merge to trunk
Hello All, Is it possible to create a user who can check in content to branches but cannot merge to trunk? I see tags in fossil-scm.org like pending-review so does that mean committers just put code there as a polite thing to do but they COULD put it in trunk? Under /setup_ulist I see iCheck-In: Commit new versions in the repository Thanks, jungle -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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] Prevent merge to trunk
Hi Warren, On 26 February 2015 at 17:36, Warren Young w...@etr-usa.com wrote: It’s like patch(1) except that it doesn’t have any of the limitations of patch as compared to the Fossil DB: a Fossil bundle file records file renames, branch tags, checkin history, etc. When I arm-twisted drh into adding this feature, I called it the uber-patch feature. :) He prefers to call it the drive-by patch feature, or bundles. Thanks for your reply and explanation! I asked a week or so about the so called drive-by patch but didn't get a response. Glad to actually get a name to it now. https://www.fossil-scm.org/index.html/help?cmd=bundle I had a feeling commit access = commit access regardless of branch/trunk so thank you and Stephan for confirming. Thanks again, jungle -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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] Prevent merge to trunk
On Feb 26, 2015, at 4:00 PM, jungle Boogie jungleboog...@gmail.com wrote: Is it possible to create a user who can check in content to branches but cannot merge to trunk? I think you want to give the new fossil bundle commands a try. Instead of giving untrusted outsiders commit access, you tell them to clone your public repo, make their changes, then say something like: fossil bundle export my-experiment.bundle --branch my-experiment Then they send you the bundle file, which you temporarily apply to your local clone with a command like: fossil bundle import my-experiment.bundle If they created a branch like the example above, you’d check out that branch and inspect the changes. Otherwise you’d be using “fossil diff --from ... “ and such. If you’re happy with the changes, you publish them with “import --publish”. Otherwise, you say fossil bundle purge my-experiment.bundle It’s like patch(1) except that it doesn’t have any of the limitations of patch as compared to the Fossil DB: a Fossil bundle file records file renames, branch tags, checkin history, etc. When I arm-twisted drh into adding this feature, I called it the uber-patch feature. :) He prefers to call it the drive-by patch feature, or bundles. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
