On Wed, 11 Feb 2015 16:21:32 +0100, Richard Hipp d...@sqlite.org wrote:
You can now access the Fossil self-hosting repository using the San
Francisco Modern skin at:
https://www.fossil-scm.org/skin2
Please let me know if you see any problems with the look of this
alternative skin.
On Wed, Feb 11, 2015 at 7:54 AM, Richard Hipp d...@sqlite.org wrote:
Fossil uses file mtimes and sizes to help it detect changes. When
your tool moves foo to foo.bak, this changes neither the mtime or the
size. So Fossil fails to detect the change, by default.
But, the new foo.bak would
On Wed, Feb 11, 2015 at 10:34 AM, Stephan Beal sgb...@googlemail.com
wrote:
The infrastructure is there to support merging wikis content just like
other content, but the logic/code is missing for such handling of wiki
pages and tickets. Your proposal would add a lot of logic for wikis which
Thus said Richard Hipp on Wed, 11 Feb 2015 10:21:32 -0500:
https://www.fossil-scm.org/skin2
Please let me know if you see any problems with the look of this
alternative skin.
One other thing I've noticed is that the second-level menu in the
Timeline page doesn't line up
On 2/11/15, Ron W ronw.m...@gmail.com wrote:
As I understand it, the only thing missing during the commit of a wiki
page is identification of the parent commit.
The P-card on the Wiki artifact
(https://www.fossil-scm.org/skin2/doc/trunk/www/fileformat.wiki#wikichng)
shows the parent(s) of
On Wed, Feb 11, 2015 at 5:14 PM, Ron W ronw.m...@gmail.com wrote:
On Wed, Feb 11, 2015 at 7:54 AM, Richard Hipp d...@sqlite.org wrote:
Fossil uses file mtimes and sizes to help it detect changes. When
your tool moves foo to foo.bak, this changes neither the mtime or the
size. So Fossil
Hi J.,
On 11 February 2015 at 08:23, j. van den hoff veedeeh...@googlemail.com wrote:
On Wed, 11 Feb 2015 16:21:32 +0100, Richard Hipp d...@sqlite.org wrote:
You can now access the Fossil self-hosting repository using the San
Francisco Modern skin at:
https://www.fossil-scm.org/skin2
On 11 February 2015 at 07:50, jungle Boogie jungleboog...@gmail.com wrote:
Context is wrapping the date onto two lines:
https://www.fossil-scm.org/skin2/info/327eee14525ff1c9
Looks like this occurs here too:
https://www.fossil-scm.org/skin2/finfo?name=src/info.c
It's not broken but makes it
Thus said Richard Hipp on Wed, 11 Feb 2015 10:21:32 -0500:
https://www.fossil-scm.org/skin2
Please let me know if you see any problems with the look of this
alternative skin.
Looks nice, except it has no background color. Perhaps this is
intentional?
Andy
--
TAI64
On Wed, 11 Feb 2015 18:06:24 +0100, jungle Boogie
jungleboog...@gmail.com wrote:
Hi J.,
On 11 February 2015 at 08:23, j. van den hoff
veedeeh...@googlemail.com wrote:
On Wed, 11 Feb 2015 16:21:32 +0100, Richard Hipp d...@sqlite.org wrote:
You can now access the Fossil self-hosting
You can now access the Fossil self-hosting repository using the San
Francisco Modern skin at:
https://www.fossil-scm.org/skin2
Please let me know if you see any problems with the look of this
alternative skin.
--
D. Richard Hipp
d...@sqlite.org
Richard,
Thanks a lot!
Best Regards,
Zoltan
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
On 2/11/15, j. van den hoff veedeeh...@googlemail.com wrote:
whatever the reason, the netbsd example (a worst case scenario, really)
would suggest to chose 12 instead of 10 as the future default length
to avoid collisions these next some hundred years.
Maybe the default prefix lengths should
On Wed, 11 Feb 2015 15:24:04 +0100, Joerg Sonnenberger
jo...@britannica.bec.de wrote:
On Wed, Feb 11, 2015 at 02:13:10PM +0100, j. van den hoff wrote:
for the netbsd repo (presuming there are half a million checkins in it)
Hash conflicts likely count all artifacts, so it would be more like
On Wed, Feb 11, 2015 at 4:18 PM, David Mason dma...@ryerson.ca wrote:
While we're at it. I would *really* like to have merging of wiki
pages upon sync. Ideal would be for any conflict to produce a warning
at sync time and to add to a table that would be visible in the wiki
tab on the ui,
While we're at it. I would *really* like to have merging of wiki
pages upon sync. Ideal would be for any conflict to produce a warning
at sync time and to add to a table that would be visible in the wiki
tab on the ui, with the page removed from that table upon edit.
../Dave
On 31 January 2015
On Wed, 11 Feb 2015 16:21:32 +0100, Richard Hipp d...@sqlite.org wrote:
You can now access the Fossil self-hosting repository using the San
Francisco Modern skin at:
https://www.fossil-scm.org/skin2
Please let me know if you see any problems with the look of this
alternative skin.
the
Hi Richard,
On 11 February 2015 at 07:21, Richard Hipp d...@sqlite.org wrote:
You can now access the Fossil self-hosting repository using the San
Francisco Modern skin at:
https://www.fossil-scm.org/skin2
Please let me know if you see any problems with the look of this
alternative skin.
On Wed, 11 Feb 2015 15:23:55 +0100, Richard Hipp d...@sqlite.org wrote:
On 2/11/15, j. van den hoff veedeeh...@googlemail.com wrote:
whatever the reason, the netbsd example (a worst case scenario, really)
would suggest to chose 12 instead of 10 as the future default length
to avoid collisions
Dears,
I'm new to Fossil, but after I heard about it on FLOSS weekly, I got very
interested in it, it pushed all of the right buttons for me: Distribution,
self containment, wiki, ticketing, version control.
It's a dream come true, and all of this in a fine customizable package!
(I'm trying a
On Wed, Feb 11, 2015 at 4:32 PM, Fadi Mansour
fadi.redeemer.mans...@gmail.com wrote:
The first issue I had, is that I was not sure where to point my questions
other than this mailing list.
So, first of all, is it Ok to post questions here?
Indeed - this is _the_ forum for fossil (aside
On 2/11/15, j. van den hoff veedeeh...@googlemail.com wrote:
On Wed, 11 Feb 2015 16:21:32 +0100, Richard Hipp d...@sqlite.org wrote:
You can now access the Fossil self-hosting repository using the San
Francisco Modern skin at:
https://www.fossil-scm.org/skin2
the box for specifying the
On Wed, Feb 11, 2015 at 3:33 PM, Andreas Kupries andre...@activestate.com
wrote:
AFAIK wiki pages have no parent.
The various commits to a specific page P are simply _time_ordered_
under the name of the page.
That's my point. The web UI's wiki editor page does not have the ID of the
commit
On 2/11/2015 6:23 AM, Richard Hipp wrote:
On 2/11/15, j. van den hoff veedeeh...@googlemail.com wrote:
whatever the reason, the netbsd example (a worst case scenario, really)
would suggest to chose 12 instead of 10 as the future default length
to avoid collisions these next some hundred years.
AFAIK wiki pages have no parent.
The various commits to a specific page P are simply _time_ordered_
under the name of the page.
IOW wiki pages have no full-blown branching system, etc.
Hence also the impossibility of 'merging' changes.
On Wed, Feb 11, 2015 at 12:03 PM, Ron W
On Wed, Feb 11, 2015 at 12:19 PM, Richard Hipp d...@sqlite.org wrote:
The P-card on the Wiki artifact
(https://www.fossil-scm.org/skin2/doc/trunk/www/fileformat.wiki#wikichng)
shows the parent(s) of each Wiki commit. This has always been
recorded.
In Fossil version [3e5ebe2b90], when
On 2/11/15, Ross Berteig r...@cheshireeng.com wrote:
On 2/11/2015 6:23 AM, Richard Hipp wrote:
On 2/11/15, j. van den hoff veedeeh...@googlemail.com wrote:
whatever the reason, the netbsd example (a worst case scenario, really)
would suggest to chose 12 instead of 10 as the future default
On Wed, Feb 11, 2015 at 9:21 AM, Richard Hipp d...@sqlite.org wrote:
You can now access the Fossil self-hosting repository using the San
Francisco Modern skin at:
https://www.fossil-scm.org/skin2
Please let me know if you see any problems with the look of this
alternative skin.
Looks
On Wed, Feb 11, 2015 at 10:21:32AM -0500, Richard Hipp wrote:
You can now access the Fossil self-hosting repository using the San
Francisco Modern skin at:
https://www.fossil-scm.org/skin2
Please let me know if you see any problems with the look of this
alternative skin.
Look
Working w/ various combinations and permutations of complex(ish)
builds, a ./configure phase for me will generate a config.old, and
even though it's a good rule to not put build artifacts into version
control, I do put the config.old in so I have an in-tree reference to
changes from previous
a) having a .bak file completely undermines the reason for using
source control. It reveals old habits from pre-SCM days, which are no
longer relevant once one has an SCM.
Not necessarily. If the tool *needs* the file and the .bak file, then
you need to keep both around and you'd better put
On Wed, Feb 11, 2015 at 09:39:06AM +0100, Gour wrote:
which is very strange considering that on the remote server the Fossil
binary is in $HOME/bin which is in my $PATH.
Non-interactive ssh doesn't process .profile, only the PATH list in
ssh_config.
Joerg
I'm trying to push to my remote server using SSH protocol:
fossil push --verbose
ssh://userid@host//absolute/path/to/the/fossil/repo/fossil.fossil
Bytes Cards Artifacts Deltas
waiting for server...bash: fossil: command not found
server did not reply
Then I tried by
Gour g...@atmarama.net writes:
Any hint?
Uhh...I was ble to decipher correct syntax:
I forgot to add that I can push via https:
fossil push ssh://uid@host//abs/path/repo.fossil\?fossil=/path/to/bin/fossil
Excuse me for the noise. :-(
Sincerely,
Gour
--
Abandoning all attachment to
On Wed, 11 Feb 2015 01:21:22 +0100, Warren Young w...@etr-usa.com wrote:
On Feb 10, 2015, at 4:34 PM, Richard Hipp d...@sqlite.org wrote:
On 2/10/15, Warren Young w...@etr-usa.com wrote:
Seems like a risky gamble to me.
Risk? It's a low-probability of a minor ambiguity in the display
On Tue, Feb 10, 2015 at 06:38:02PM -0800, bch wrote:
For the record, what Mr Beal is talking about is called a scheme
relative URI -- which I know about since an HTTP parser I work with
handles them so poorly. However, if your browser works w/ (eg)
Wikipedia, you are already using
On Wed, Feb 11, 2015 at 11:18 AM, Joerg Sonnenberger
jo...@britannica.bec.de wrote:
On Tue, Feb 10, 2015 at 06:38:02PM -0800, bch wrote:
For the record, what Mr Beal is talking about is called a scheme
relative URI -- which I know about since an HTTP parser I work with
handles them so
On 2/11/15, j. van den hoff veedeeh...@googlemail.com wrote:
I'd say one can live with this potential annoyance (not danger) of getting
a collision of the sub-hashes
even with 10 digits (although 12 would mean that for the foreseeable
future number of actual collisions
in all existing fossil
On Tue, Feb 10, 2015 at 6:42 PM, Richard Hipp d...@sqlite.org wrote:
I keep most of my Fossil repos in a common directory: ~/www/repos. I
currently have 64 of them sitting there.
A tip for those _not_ using their own web server (e.g. for those using CGI
over apache): keep your repos OUT of
I use fossil version 1.29
I have a project where there's a file, simple text.
That file is manipulated by a tool. The tool always keeps the previous
version of the file, renaming it.
So, we have a file 'foo' and 'foo.bak' and whenever foo changes, the
old version of foo is renamed to foo.bak
On Wed, 11 Feb 2015 12:56:58 +0100, Richard Hipp d...@sqlite.org wrote:
On 2/11/15, j. van den hoff veedeeh...@googlemail.com wrote:
I'd say one can live with this potential annoyance (not danger) of
getting
a collision of the sub-hashes
even with 10 digits (although 12 would mean that for
On 2/11/15, Zoltán Kócsi zol...@bendor.com.au wrote:
I use fossil version 1.29
I have a project where there's a file, simple text.
That file is manipulated by a tool. The tool always keeps the previous
version of the file, renaming it.
So, we have a file 'foo' and 'foo.bak' and whenever foo
42 matches
Mail list logo
