FINFO (Usage: fossil finfo ?OPTIONS? FILENAME) is one of the most useful
features of fossil as it accepts a filename and provides its history of changes
(unfortunately, it does not follow possible file renames, but that’s another
issue).
What I would like is to have the possibility to also
On Fri, Oct 17, 2014 at 2:59 AM, Ron W ronw.m...@gmail.com wrote:
A question about libfossil: Is it possible to directly create a delta
artifact? I ask this because it looks like SVN::Dump::Reader does not
un-delta the artifact content. So either I would have to apply the delta
myself (to
On Fri, Oct 17, 2014 at 8:34 AM, Tony Papadimitriou to...@acm.org wrote:
Would that be too much programming effort to add? I.e., check if
‘filename’ is a directory and in that case return FINFO for all associated
files.
If it weren't for the -status and -print options, it would require
On Fri, Oct 17, 2014 at 10:16 AM, Tony Papadimitriou to...@acm.org wrote:
Not being sure I understood your approach completely, and without
knowing fossil’s internals, but knowing that it uses SQL for a lot of its
work, I think that mostly the related SQL would have to change.
I believe a
On Thu, Oct 16, 2014 at 9:24 PM, Ron W ronw.m...@gmail.com wrote:
On Thu, Oct 16, 2014 at 3:14 AM, Stephan Beal sgb...@googlemail.com
wrote:
i'm not aware of any WWW feature of fossil which uses checkout-level
data except maybe to display versioned settings.
For embedded documents:
On Thu, 16 Oct 2014 20:59:52 -0400
Ron W ronw.m...@gmail.com wrote:
For a project that follows the recommended convention of directories
named trunk, branches and tags - or clearly identifies its
convention - creating branches (and tagged commits) in Fossil should
not be too hard. If the
On Fri, Oct 17, 2014 at 09:59:26AM +0200, Stephan Beal wrote:
On Fri, Oct 17, 2014 at 8:34 AM, Tony Papadimitriou to...@acm.org wrote:
Would that be too much programming effort to add? I.e., check if
‘filename’ is a directory and in that case return FINFO for all associated
I guess the timeline equivalent would work, too! However, I'd be more
interested in being able to see just the code changes (i.e., check-ins) and
not all the 'noise' about wiki edits, tickets, tags, etc which the timeline
gives by default (unless one uses the -t ci option). So, I thought
On Fri, Oct 17, 2014 at 10:17 AM, to...@acm.org wrote:
I guess the timeline equivalent would work, too!
Please try out the change on the cmdline-timeline-enhancement branch and
see if it works for you.
--
D. Richard Hipp
d...@sqlite.org
___
On Fri, Oct 17, 2014 at 05:17:24PM +0300, to...@acm.org wrote:
snip
I guess the timeline equivalent would work, too! However, I'd be
more interested in being able to see just the code changes (i.e.,
check-ins) and not all the 'noise' about wiki edits, tickets, tags,
etc which the
On Fri, Oct 17, 2014 at 11:32:27AM -0400, Richard Hipp wrote:
On Fri, Oct 17, 2014 at 10:17 AM, to...@acm.org wrote:
I guess the timeline equivalent would work, too!
Please try out the change on the cmdline-timeline-enhancement branch
and see if
it works for you.
Nice,
On Fri, Oct 17, 2014 at 12:01 PM, Martin Gagnon eme...@gmail.com wrote:
I guess the next step is to have that feature on the /timeline web page,
and may be a timeline link beside each directory in the /tree web
page..
That's harder to do because the graph is disjoint when you skip
On Fri, Oct 17, 2014 at 12:05:36PM -0400, Richard Hipp wrote:
On Fri, Oct 17, 2014 at 12:01 PM, Martin Gagnon eme...@gmail.com wrote:
I guess the next step is to have that feature on the /timeline web page,
and may be a timeline link beside each directory in the /tree web
I was thinking this scenario to implement, Add, Commit, Push ... in this way:
One host A uses JSON to communicate whit another host B, host B should be
http://localhost:8080 (mainly), so due to Javascript and JSON normally runs
on client side, when i for example do AJAX with JSON where
On Fri, Oct 17, 2014 at 6:39 PM, Carlos Alberto Ruiz Uribe
carlos.ru...@softtek.com wrote:
So build a Web client on a remote server will have sense, on otherwise,
even a Web Client inside the Fossil pages will make sense, doesn’t it?
It does make sense, but the security implications make
I did a quick try, and it seems to work OK with only one small exception, the
root directory itself (where _FOSSIL_ is).
There, “fossil tim .” for example (which works OK in subdirectories), shows
nothing “+++ no more data (0) +++” when obviously there is quite a lot because
if I give “fossil
One more problem I see is that it sometimes shows the same timeline entry
multiple times in a row (same SHA1 and description)
From: to...@acm.org
Sent: Friday, October 17, 2014 7:51 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FINFO suggestion
I did a quick try, and it
You're right about security holes or issues, but what i mean is : Web client is
just sending JSON commands to a local host that operates locally, the
operations are not on internet , i mean it will be like to send remote
commands to a local Fossil CLI, something like that but using http as
On Fri, Oct 17, 2014 at 7:36 PM, Carlos Alberto Ruiz Uribe
carlos.ru...@softtek.com wrote:
*You’re right about security holes or issues, but what i mean is : Web
client is just sending JSON commands to a local host that operates locally,
the operations are not on internet ,*
But the API
An observation related to the last problem. The identical multiple entries
seem to match the number of files that have changed in that subdirectory. So,
if three files changed, the same timeline entry appears three times.
From: to...@acm.org
Sent: Friday, October 17, 2014 8:30 PM
To: Fossil
Hello,
I just noticed something which I can't recall seeing before. I
started fossil ui on a repository (-R foo.fossil), and when I hit
ctrl-c, it terminated as expected, but it left the corresponding -shm
and -wal files. I'm pretty sure I have used fossil ui on wal'd fossil
repository
On 17/10/14 20:01, Jan Danielsson wrote:
[.. -wal -shm remain after ctrl-c:ing out of fossil ui ..]
A quick grep through the source leads me to believe that there is no
registered signal handler to handle SIGINT apart from when an sqlite
shell is started. Which leaves me slightly surprised
On Fri, Oct 17, 2014 at 08:57:50PM +0300, to...@acm.org wrote:
An observation related to the last problem. The identical multiple
entries seem to match the number of files that have changed in that
subdirectory. So, if three files changed, the same timeline entry
appears three times.
On Thu, Oct 16, 2014 at 8:59 PM, Ron W ronw.m...@gmail.com wrote:
After doing some research,
More research...
In the SVN dump file, deltas are optional, so an initial implementation can
omit dealing with deltas.
SVN dump files do not have manifests. There is a revision artifact followed
by
Seems to work much better. I no longer get duplicates. Thanks. (I haven't
yet checked whether the entries I see are the correct ones, e.g., no missing
ones, but on first inspection the timeline seems correct).
So, for now the only remaining problem I can see is the failure to show any
On Fri, Oct 17, 2014 at 3:25 PM, Ron W ronw.m...@gmail.com wrote:
More research...
Needing a break from dump file processing, I decided to look in to how a
mirror could be kept up to date.
I previously mentioned using a commit monitor, so I looked to see how one
SVN repo could mirror another.
On Fri, Oct 17, 2014 at 08:10:10PM +0200, Jan Danielsson wrote:
On 17/10/14 20:01, Jan Danielsson wrote:
[.. -wal -shm remain after ctrl-c:ing out of fossil ui ..]
A quick grep through the source leads me to believe that there is no
registered signal handler to handle SIGINT apart from
On Fri, Oct 17, 2014 at 10:43:53PM +0300, to...@acm.org wrote:
Seems to work much better. I no longer get duplicates. Thanks. (I
haven't yet checked whether the entries I see are the correct ones,
e.g., no missing ones, but on first inspection the timeline seems
correct).
So, for now the
This new timeline functionality really makes a huge difference in everyday
work! Thank you all.
-Original Message-
From: Martin Gagnon
On Fri, Oct 17, 2014 at 10:43:53PM +0300, to...@acm.org wrote:
So, for now the only remaining problem I can see is the failure to
show any changes
On Fri, Oct 17, 2014 at 11:47:53PM +0300, to...@acm.org wrote:
OK, here's one more minor issue you can easily test with sqlite3
repo under Windows. Windows filenames are case insensitive. Trying
with wrong case
snip
This one is fixed now too..
--
Martin G.
Last change with case sensitivity for Windows works great.
One note about the previous fix regarding the repo root. It assumes (based
on comment in source) equivalence to no filename given. But this prints
'noise' like tickets, wiki edits, etc.
So, I guess a simple fix is to force enable the
On Fri, 17 Oct 2014 16:00:08 -0400
Ron W ronw.m...@gmail.com wrote:
Hello Ron,
Needing a break from dump file processing, I decided to look in to
how a mirror could be kept up to date.
Thank you very much for taking time in doing this research...
Although this sounds like a Rube Goldberg
On Oct 15, 2014, at 2:18 PM, Stephan Beal sgb...@googlemail.com wrote:
checkin [da524a7b522f] @ 2014-10-15 22:13:19 by [stephan] branch [trunk]
initial chicken.
On April 1, Fossil should use this as its default comment for commits to new
trees.
Again, thanks for the quick fix regarding forced -t ci on filename. Works
perfectly. As far as I can tell this new feature is complete! Great work!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
On Sat, 18 Oct 2014 00:12:07 +0200, Warren Young war...@etr-usa.com
wrote:
On Oct 15, 2014, at 2:18 PM, Stephan Beal sgb...@googlemail.com wrote:
checkin [da524a7b522f] @ 2014-10-15 22:13:19 by [stephan] branch [trunk]
initial chicken.
On April 1, Fossil should use this as its
On Fri, Oct 17, 2014 at 5:35 PM, Gour g...@atmarama.net wrote:
On Fri, 17 Oct 2014 16:00:08 -0400
Ron W ronw.m...@gmail.com wrote:
Needing a break from dump file processing, I decided to look in to
how a mirror could be kept up to date.
Thank you very much for taking time in doing this
On Fri, Oct 17, 2014 at 6:30 PM, Ron W ronw.m...@gmail.com wrote:
The main information the post commit hook method risks loosing is the
relationship between a copied file and its copy, but Fossil doesn't have a
copy command, so doesn't keep this, though I'm pretty sure it could.
Err, was too
On Fri, Oct 17, 2014 at 6:42 AM, Gour g...@atmarama.net wrote:
In any case, my opinion is that having SVN --- Fossil is much more
interested than Git --- Fossil 'cause, imho, with Fossil one can make
very familiar/similar workflow like the one used with SVN.
Some SVN features not in Fossil:
38 matches
Mail list logo
