Re: [fossil-users] Patch to fix "fossil export" and "fossil import"

Hi, > Please note these are clean reverse engineered dedes independent of the > code in the git using the code analysis result included. Of course, I meant s/dedes/codes/ > The default of the quoting flag is FALSE. The meaning of the conversion rule > indicators are the following: Hmmm...

Re: [fossil-users] mark offeset: fossil export and import and re-export

On Sat, Oct 15, 2016 at 05:59:50AM +0900, Osamu Aoki wrote: > These 2 files should be the same ... I hoped but reality is a bit > complicated. They are very similar but the mark field is strange. No, the marks are derived from the rid and those again depend on the order in which blobs are added.

[fossil-users] Patch to fix "fossil export" and "fossil import"

Hi, I have a set of working patches for "fossil export" and "fossil import" as attached. Please note these are clean reverse engineered dedes independent of the code in the git using the code analysis result included. These codes are BSD-2-Clause licensed and I agree to copyright assignment to

[fossil-users] mark offeset: fossil export and import and re-export

Hi, As a part of sanity check, I made an export of fossil archive to a file and back into another fossil archive ... and re-export to a file. These 2 files should be the same ... I hoped but reality is a bit complicated. They are very similar but the mark field is strange. The initial export

[fossil-users] Build should be continued for unknown options

Hi, Here is a trivial patch to build the source tree even with unknown options for autosetup/autosetup but make sure to warn user. The idea is from Barak A. Pearlmutter. Regards, Osamu PS: re-send from subscribed addess From: "Barak A. Pearlmutter" Date: Sun, 9 Oct 2016

Re: [fossil-users] Build should be continued for unknown options

On 15 October 2016 at 05:26, Steven Gawroriski wrote: > On Sat, 15 Oct 2016 05:59:23 +0900 > Osamu Aoki wrote: > > > Hi, > > > > Here is a trivial patch to build the source tree even with unknown > > options for autosetup/autosetup but make sure

[fossil-users] Solved: Build ...

Hi, On Sat, Oct 15, 2016 at 10:27:44AM +1000, Steve Bennett wrote: > autosetup already supports --disable-option-checking (like autoconf) > Why wouldn't that be good enough? Thanks. This makes sense. I will ask Debian package to use it. This is cleaner approach. Also, I will double check

[fossil-users] autosetup: hidden autoconf/automake compatibility

Hi, Here is FYI suggestion to make compatibility of autosetup to support the system expecting typical autoconf/automake options while not killing nice option checking feature of autosetup via --disable-option-checking. As I see output of "./configure --help" on autoconf/automake based code, I

Re: [fossil-users] How to make post-commit hook?

(Thu, 13 Oct 08:25) Nickolas Lloyd: > At a cursory glance, it looks like the `fsl' tool would allow you to do > something similar: just define a new `fsl' command that will do the > commit, export, and push all in one step. So, now I just use a function that imitates a post-commit hook. Not

Re: [fossil-users] Build should be continued for unknown options

> On 15 Oct 2016, at 6:59 AM, Osamu Aoki wrote: > > Hi, > > Here is a trivial patch to build the source tree even with unknown options > for autosetup/autosetup but make sure to warn user. > > The idea is from Barak A. Pearlmutter. > > Regards, > > Osamu autosetup