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
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,
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
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
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
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,
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):
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:
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
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
(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
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
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
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
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
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
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
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
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
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
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
21 matches
Mail list logo
