On Tue, Jun 28, 2016 at 1:34 PM, Warren Young wrote:
>
> 5. My scheme modifies one of the input source files — as opposed to
> modifying the built executable, as in Ron W’s scheme — which means you
> could have an executable that claims to be built against the prior checkin
> on the current branc
Ah...Let's play YOUR game then.People ask for something then you ask others to
follow because it seems that most people (let say : five or more?) guys speak
about it ?And of course those guys are EXPERT (or I suppose according to you or
the fossil team or whoever you want) so everyone should fol
A recent post[1] mentioned one scheme for inserting the Fossil checkin ID for
the sources used to build a given executable into the executable itself, for
various good reasons.
I have a similar scheme, which I thought I’d present here. This shell script
is executed at the end of each successfu
On Mon, Jun 27, 2016 at 2:39 PM, followait wrote:
> In such an scm with GUI, one can:
> 1. diff / merge / rebase by draging one commit to another
> 2. more generally, everything can be done in the GUI, it can be intuitive
> enough, so that no doc is needed
> 3. by the easy usage and full functio
If a built-in forum existed(yay), would users be allowed to upload images
to support their posts/queries/tickets? And if so, could those attachments
be treated less strictly regarding shunning? Deleting occasional
spammer/bot entries will be required.
On Tue, Jun 28, 2016 at 9:40 AM, Warren Young
OS/ File system repair of a large image file (such as fossil's) is the way
ahead?
I say that because I would imagine it better implemented as a fossil background
activity communicating with a replica elsewhere.
Sent from my iPhone
> On Jun 28, 2016, at 8:30 AM, Karel Gardas wrote:
>
> You n
On Jun 28, 2016, at 7:50 AM, Paul Hammant wrote:
>
> OS/ File system repair of a large image file (such as fossil's) is the way
> ahead?
I don’t believe Fossil has any built-in self-repair facilities. It just checks
itself for consistency at various points in its operation and refuses to
co
On Jun 27, 2016, at 9:04 PM, Jonathan Otsuka wrote:
>
> adding a mailing list feature isn’t too far fetched.
>
> Has this idea been brought up before?
drh has publicly stated that he would like to write his own email server.[1]
However, given Fossil’s nature, I think a web forum might be bette
You need to use something like RAID1 setup with N drives using either
ZFS or btrfs. If you are on dragonfly bsd probably hammer does that
too. Also backup and scrub your disk array quite often...
Ah, just found out that zfs/btrfs is also cited by the article so you
already know that...
On Tue, Ju
Bitrot -
http://arstechnica.com/information-technology/2014/01/bitrot-and-atomic-cows-inside-next-gen-filesystems/
- data in SSD or HD being corrupted by (say) nutrinos over time. See also a
guy/gal lamenting their corrupted photo collection -
https://blog.barthe.ph/2014/06/10/hfs-plus-bit-rot/
An
Hi,
I would like to see the changes introduced just by single check-in as applied
to the current (or even an arbitrary) version.
I suppose this would be the same as trying to see which lines would be affected
if I were to do a MERGE with the –BACKOUT option
A diff with –from and –to version sh
11 matches
Mail list logo