2012/11/25 Richard Hipp d...@sqlite.org:
2012/11/25 Jan Nijtmans jan.nijtm...@gmail.com:
Stefan, I committed your patch to the bellon-unicode branch.
Feedback welcome! At first sight, looks good to me.
Stefan, please fill out
On Mon, 26 Nov, Jan Nijtmans wrote:
Finally, I had a look at the bellon-unicode branch. I like the new
--no-warnings flag, being less dangerous as the --force flag.
The question is whether the naming of this new option is a good one
(now would be the time to change it rather than after this
Hi,
I'm considering droping Drupal and move to using fossil also as a CMS.
1) How difficult is it to port a Drupal theme to fossil? I have a nivo
slider ( http://nivo.dev7studios.com/ ) on my homepage - will it work in
fossil?
Does fossil have following features, and if not, what are the
2012/11/26 Stefan Bellon sbel...@sbellon.de:
On Mon, 26 Nov, Jan Nijtmans wrote:
Finally, I had a look at the bellon-unicode branch. I like the new
--no-warnings flag, being less dangerous as the --force flag.
The question is whether the naming of this new option is a good one
Agreed,
Fossil, like many other VCSes, compresses revisions internally, and stores
only some sort of deltas. I don't know how it is actually done, but usually,
it's some sort of patches.
FYI
http://www.fossil-scm.org/index.html/doc/trunk/www/delta_encoder_algorithm.wiki
On Mon, 26 Nov 2012 16:06:31 +0200
Zeev Pekar z.pe...@gmail.com wrote:
Hi,
I'm considering droping Drupal and move to using fossil also as a CMS.
I've done some experimenting with this idea. In my mind the jury is
still out. One problem is images. Most browsers will make potentially
many
On 11/22/2012 5:05 AM, Richard Hipp wrote:
Fossil understands check-in comments and ticket text to be Wiki/HTML.
Let's say that the mimetype is text/x-fossil-wiki. This approach
worked well for us on CVSTrac (which was where many of the ideas in
Fossil originated) because it allowed hyperlinks
On Mon, Nov 26, 2012 at 2:31 PM, Ross Berteig r...@cheshireeng.com wrote:
On 11/22/2012 5:05 AM, Richard Hipp wrote:
Fossil understands check-in comments and ticket text to be Wiki/HTML.
Let's say that the mimetype is text/x-fossil-wiki. This approach
worked well for us on CVSTrac (which
IMO this should be resolved per-server configuration. Consider the
risk of XSS attacks: simply treating all comments as text/plain
automatically mitigates any past XSS attack attempts. Granted, XSS
attacks are not very likely given that few users can be expected to
have commit access...
I would
In my workflow each commit is associated with a ticket. This provides
me with requirement tracking and traceability from the
requirements/tasks/defects stored in tickets to the code or data
changes in the repository. So like Ross I would like the
functionality using the [hashcode] to be
IIUC the main reason to want a DLL instead of having to spawn a new
process for every operation is iOS. I hear that the dearth of
excellent git (and other) SCM clients for iOS has to do with the
constrained nature of the run-time environment.
___
On Mon, Nov 26, 2012 at 01:52:53PM -0600, Nico Williams wrote:
IIUC the main reason to want a DLL instead of having to spawn a new
process for every operation is iOS. I hear that the dearth of
excellent git (and other) SCM clients for iOS has to do with the
constrained nature of the run-time
On Mon, Nov 26, 2012 at 2:59 PM, Lluís Batlle i Rossell vi...@viric.namewrote:
fossil uses fork() quite enough, and its memory management depends on
that, for
what I understand.
The fossil ui and fossil server commands use fork() on unix. But
fork() is not available on windows so we have
On 11/26/12 21:06, Richard Hipp wrote:
fossil uses fork() quite enough, and its memory management depends on
that, for
what I understand.
The fossil ui and fossil server commands use fork() on unix. But
fork() is not available on windows so we have the winhttp.c source file to
work around
On Mon, Nov 26, 2012 at 3:28 PM, Jan Danielsson
jan.m.daniels...@gmail.comwrote:
When I downloaded the win32 fossil binary and installed it on a
64-bit windows, I noticed that the fossil ui won't work properly due to
that it fails to launch new processes. Running command line fossil
On Thu, Nov 22, 2012 at 10:40:32PM -0500, James Turner wrote:
NetSurf [0] is probably a lesser known browser, but I run it on my
Lemote Yeeloong, which is mips based and doesn't support larger browsers
like Firefox under OpenBSD. It might be nice to have it added. Thanks.
[0]
Am Montag, 26. November 2012, 09:08:21 schrieb Andreas Kupries:
Fossil, like many other VCSes, compresses revisions internally, and stores
only some sort of deltas. I don't know how it is actually done, but
usually, it's some sort of patches.
FYI
17 matches
Mail list logo
