hi,
I want to report the following observation:
`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.
example: doing
fossil finfo -b BUILD.txt
in the Fossil
Hi Sam.
Welcome aboard. I think Fossil is excellent, and I hope you will too.
I'm typing on a mobile device ATM, so please excuse the brevity and
spelling errors.
I use fossil for all my personal projects, as well as professionally. For
personal projects, I make a project-specific dir under my
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 JoeDoe
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'
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
On Thu, Aug 8, 2013 at 10:47 AM, Rene renew...@xs4all.nl 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
On Thu, 08 Aug 2013 10:58:58 +0200, Stephan Beal sgb...@googlemail.com
wrote:
On Thu, Aug 8, 2013 at 10:47 AM, Rene renew...@xs4all.nl wrote:
-R seems redundant.
It's not _entirely_ redundant - in some cases it changes how the
arguments
are processed. Yes, there are inconsistencies
On Thu, 08 Aug 2013 09:53:52 +0200, Andy Bradford
amb-sendok-1378540432.bggbdoanfmpdfnjoo...@bradfords.org 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
On Thu, 08 Aug 2013 12:23:56 +0200, Stephan Beal sgb...@googlemail.com
wrote:
On Thu, Aug 8, 2013 at 12:14 PM, Stephan Beal sgb...@googlemail.com
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
On Thu, Aug 8, 2013 at 1:38 PM, j. van den hoff
veedeeh...@googlemail.comwrote:
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
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 Wed, Aug 7, 2013 at 11:23 PM, Themba Fletcher
themba.fletc...@gmail.com 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
On Thu, Aug 8, 2013 at 2:32 PM, Stestagg stest...@gmail.com 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
On Thu, 08 Aug 2013 17:00:08 +0200, Stephan Beal sgb...@googlemail.com
wrote:
On Thu, Aug 8, 2013 at 2:32 PM, Stestagg stest...@gmail.com 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
On Thu, Aug 8, 2013 at 5:13 PM, j. van den hoff
veedeeh...@googlemail.comwrote:
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
One of the problems is that the help given by fossil help command 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
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
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
On 2013-08-08 10:58, Stephan Beal wrote:
On Thu, Aug 8, 2013 at 10:47 AM, Rene renew...@xs4all.nl 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 Thu, 08 Aug 2013 22:25:33 +0200, Chad Perrin c...@apotheon.net 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.
On Thu, 08 Aug 2013 19:49:18 +0200, Richard Hipp d...@sqlite.org wrote:
On Thu, Aug 8, 2013 at 12:40 PM, Julian j...@ptolserv.com wrote:
One of the problems is that the help given by fossil help command
isn't
always complete. For example the help for checkin (fossil help ci),
doesn't
list
On Thu, Aug 8, 2013 at 9:18 PM, Themba Fletcher
themba.fletc...@gmail.comwrote:
of the historical features are just going to have to go. cough plaintext
passwords in database cough :)
FWIW: i learned a great deal about password handling from Fossil when i
integrated the JSON API into Fossil's
On Thu, Aug 8, 2013 at 10:48 PM, j. van den hoff
veedeeh...@googlemail.comwrote:
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
On Thu, Aug 8, 2013 at 10:29 PM, Rene renew...@xs4all.nl 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
On Thu, 08 Aug 2013 23:12:52 +0200, Stephan Beal sgb...@googlemail.com
wrote:
On Thu, Aug 8, 2013 at 10:48 PM, j. van den hoff
veedeeh...@googlemail.comwrote:
2.
I'm not comfortable with categorically recommending to new users to
separate the database from the checkout. I know that many on
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 repo
On Thu, Aug 8, 2013 at 11:31 PM, j. van den hoff
veedeeh...@googlemail.comwrote:
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
On Thu, 08 Aug 2013 23:36:14 +0200, Stephan Beal sgb...@googlemail.com
wrote:
On Thu, Aug 8, 2013 at 11:31 PM, j. van den hoff
veedeeh...@googlemail.comwrote:
but what does this proof? the next guy might be a tidy up fanatic and
accidentally remove the directory with all the repository
28 matches
Mail list logo
