Thus said "j. van den hoff" on Thu, 08 Aug 2013 08:31:04 +0200:
> In case this e-mail wraps, I've marked the spurious lines where
> `merge' and `i' are erroneously wrapped by `fossil' to the next line.
> this happens with 1.26.
So my initial patch actually wasn't too far off. The reas
On Thu, 08 Aug 2013 23:36:14 +0200, Stephan Beal
wrote:
On Thu, Aug 8, 2013 at 11:31 PM, j. van den hoff
wrote:
but what does this proof? the next guy might be a tidy up fanatic and
accidentally remove the directory with all the repository files, right?
My point is only that that type of
On Thu, Aug 8, 2013 at 11:31 PM, j. van den hoff
wrote:
> but what does this proof? the next guy might be a tidy up fanatic and
> accidentally remove the directory with all the repository files, right?
>
My point is only that that type of goof-up happens much more often if the
files are in the sa
> i _strongly_ recommend against keeping the repo db in the same dir as a
> checkout. Very little can go wrong when they're separated and lots can go
> wrong when they're not.
>
Wholeheartedly concur. In just over two years of daily usage I've lost data
exactly once and that was due to having my r
On Thu, 08 Aug 2013 23:12:52 +0200, Stephan Beal
wrote:
On Thu, Aug 8, 2013 at 10:48 PM, j. van den hoff
wrote:
2.
I'm not comfortable with categorically recommending to new users to
separate the database from the checkout. I know that many on this list
think this to be a good thing but in
On Thu, Aug 8, 2013 at 10:29 PM, Rene wrote:
> Well lets go the other way a repo, if not in an checkout, must always be
> specified with -R.
> and maybe if a -R repo is specified in a checkout the -R takes precedent.
When a checkout is opened, its corresponding repo db is automatically
opened
On Thu, Aug 8, 2013 at 10:48 PM, j. van den hoff
wrote:
> 2.
> I'm not comfortable with categorically recommending to new users to
> separate the database from the checkout. I know that many on this list
> think this to be a good thing but in general
In fossil keeping them in the same dir can an
On Thu, Aug 8, 2013 at 9:18 PM, Themba Fletcher
wrote:
> of the historical features are just going to have to go. plaintext
> passwords in database :)
>
FWIW: i learned a great deal about password handling from Fossil when i
integrated the JSON API into Fossil's auth system. You might want to t
On Thu, 08 Aug 2013 19:49:18 +0200, Richard Hipp wrote:
On Thu, Aug 8, 2013 at 12:40 PM, Julian wrote:
One of the problems is that the help given by fossil help
isn't
always complete. For example the help for checkin (fossil help ci),
doesn't
list the --date-override or --user-override
On Thu, 08 Aug 2013 22:25:33 +0200, Chad Perrin wrote:
This "Fossil For New Users" intro to doing the basics in Fossil was a
few minutes' work, in part as a reminder for myself. I thought it might
be useful for others as well, though, so I finally decided to put it
online.
http://blogstra
On 2013-08-08 10:58, Stephan Beal wrote:
On Thu, Aug 8, 2013 at 10:47 AM, Rene wrote:
-R seems redundant.
It's not _entirely_ redundant - in some cases it changes how the
arguments are processed. Yes, there are inconsistencies there, but
some of the argument handling relies on one or the other
This "Fossil For New Users" intro to doing the basics in Fossil was a
few minutes' work, in part as a reminder for myself. I thought it might
be useful for others as well, though, so I finally decided to put it
online.
http://blogstrapping.com/?page=2013.220.13.42.53
Let me know what you thi
On Wed, Aug 7, 2013 at 2:41 PM, Stephan Beal wrote:
> On Wed, Aug 7, 2013 at 11:23 PM, Themba Fletcher <
themba.fletc...@gmail.com>
> wrote:
>>
>> I recently got a contract to rewrite a large (web) application. The
>> intent is to transition, at a measured pace, from a large collection
>> of hand-
Thus said Andy Bradford on Thu, 08 Aug 2013 13:01:33 -0600:
> 75f02948fa 2011-07-22 drh trunk Merge the recent autosetup changes int
Hmm, perhaps that isn't the right fix. I would not have expected it to
cut off at the 'o' from 'into' here: Instead I believe it should have
produced:
75f029
Thus said "j. van den hoff" on Thu, 08 Aug 2013 08:31:04 +0200:
> `finfo -b' is supposed to produce one-line abbreviations for all
> commits but in fact introduces spurious line breaks which put a single
> trailing word (or some chars) on the next line.
This would appear to be a bug in the
On Thu, Aug 8, 2013 at 12:40 PM, Julian wrote:
> One of the problems is that the help given by fossil help isn't
> always complete. For example the help for checkin (fossil help ci), doesn't
> list the --date-override or --user-override options, even though they
> appear to be accepted. The same
On Thu, Aug 8, 2013 at 6:40 PM, Julian wrote:
> The only way I've found to discover them is to use "grep find_option" on
> the source - I'm not sure that is very user-friendly.
>
It is for fossil's original intended audience ;). But, yeah, i admit that
it's not ideal.
Tell you what: look around
One of the problems is that the help given by fossil help isn't
always complete. For example the help for checkin (fossil help ci), doesn't
list the --date-override or --user-override options, even though they appear to
be accepted. The same appears to be the case for the branch command.
The
On Thu, Aug 8, 2013 at 5:13 PM, j. van den hoff
wrote:
> well that's sort of difficult for the average user I'd say since he does
> not _know_
> what the parser is doing and what the set of valid calls to fossil looks
> like. I cannot be sure,
> for instance that there are no further undocumented
On Thu, 08 Aug 2013 17:00:08 +0200, Stephan Beal
wrote:
On Thu, Aug 8, 2013 at 2:32 PM, Stestagg wrote:
I would agree here, it's not at all clear. Even when you know there is
a
--user option, then the fossil output isn't clear:
In Fossil's defense: i've been using Fossil almost daily
On Thu, Aug 8, 2013 at 2:32 PM, Stestagg wrote:
> I would agree here, it's not at all clear. Even when you know there is a
> --user option, then the fossil output isn't clear:
>
In Fossil's defense: i've been using Fossil almost daily since Christmas
2007 and haven't every used --user.
steves@
On Wed, Aug 7, 2013 at 11:23 PM, Themba Fletcher
wrote:
> Hi all,
>
> I recently got a contract to rewrite a large (web) application. The
> intent is to transition, at a measured pace, from a large collection
> of hand-written, framework-free php files to a structured setup with a
> nice MVC frame
I would agree here, it's not at all clear. Even when you know there is a
--user option, then the fossil output isn't clear:
steves@sapphire ~> f ls
fossil: current directory is not within an open checkout
# OK
steves@sapphire ~> f --user foo
fossil: fossil: unknown command: --user
fossil: use "
On Thu, 08 Aug 2013 14:03:42 +0200, Stephan Beal
wrote:
On Thu, Aug 8, 2013 at 1:38 PM, j. van den hoff
wrote:
question: should there not be a help page for fossil itself, maybe
(`fossil help fossil') which explains this sort of things?
Is this perhaps what you're looking for:
[stephan@
On Thu, Aug 8, 2013 at 1:38 PM, j. van den hoff
wrote:
> question: should there not be a help page for fossil itself, maybe
> (`fossil help fossil') which explains this sort of things?
Is this perhaps what you're looking for:
[stephan@host:~]$ f help help
Usage: f help COMMAND
or: f COMMAND
hi,
I just encountered the need to do something like
fossil --user joedoe ci
after trying `fossil ci' failed, `fossil' recommended to use the --user
flag. this flag seems nowhere to be mentioned in the builtin help pages
(I scanned all pages for the commands displayed by `fossil help -a'). I
On Thu, 08 Aug 2013 12:23:56 +0200, Stephan Beal
wrote:
On Thu, Aug 8, 2013 at 12:14 PM, Stephan Beal
wrote:
Sorry for the confusion: "don't much care for" is another way of saying
"do not like," and we agree completely that these inconsistencies are
not
ideal.
Minor clarification
On Thu, Aug 8, 2013 at 12:14 PM, Stephan Beal wrote:
> Sorry for the confusion: "don't much care for" is another way of saying
> "do not like," and we agree completely that these inconsistencies are not
> ideal.
>
Minor clarification for the non-native speakers: "don't care FOR'" means
"do not l
On Thu, Aug 8, 2013 at 11:55 AM, j. van den hoff
wrote:
> On Thu, 08 Aug 2013 10:58:58 +0200, Stephan Beal
> wrote:
>
>> context of libfossil, that's been one of the minor points on the list of
>> things to consider, and while i don't much care for inconsistency in
>> software, i _think_ that i'l
On Thu, 08 Aug 2013 09:53:52 +0200, Andy Bradford
wrote:
Thus said "j. van den hoff" on Thu, 08 Aug 2013 09:31:28 +0200:
1.in `orig.fossil'the(sole) `setup'user isme
(current_login_name), which is as it should be. (as an aside: the help
text does speak of `admin'
On Thu, 08 Aug 2013 10:58:58 +0200, Stephan Beal
wrote:
On Thu, Aug 8, 2013 at 10:47 AM, Rene wrote:
-R seems redundant.
It's not _entirely_ redundant - in some cases it changes how the
arguments
are processed. Yes, there are inconsistencies there, but some of the
argument handling r
On Thu, Aug 8, 2013 at 10:47 AM, Rene wrote:
> -R seems redundant.
It's not _entirely_ redundant - in some cases it changes how the arguments
are processed. Yes, there are inconsistencies there, but some of the
argument handling relies on one or the other approach. When the app looks
for a CLI
on some commands one has to use -R repo e.g.
sync
pull
push
and others not
clone
ui
server
-R seems redundant.
--
Rene
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-user
Thus said "j. van den hoff" on Thu, 08 Aug 2013 09:31:28 +0200:
> 1.in `orig.fossil'the(sole) `setup'user isme
> (current_login_name), which is as it should be. (as an aside: the help
> text does speak of `admin' user, but actually its the `setup' user
> (and a `admin
hi,
`fossil help clone' tells me:
8<--
By default, your current login name is used to create the default
admin user. This can be overridden using the -A|--admin-user
parameter.
8<--
I just tried that locally (within my file system):
fossil clone -A JoeDo
35 matches
Mail list logo
