Re: [fossil-users] Help with making a subroutine x-platform to windows

[Antoine Chavasse]

It seems to me it would be simpler and more robust to simply call the
relevant win32 api function:

https://docs.microsoft.com/en-us/windows/desktop/api/windns/nf-windns-dnsquery_a

On Wed, Jun 27, 2018, 23:22 Scott Doctor  wrote:

> A way may be using the system() command to run nslookup. From
> the windows command line help for the command:
>
> Commands:   (identifiers are shown in uppercase, [] means
> optional)NAME- print info about the host/domain NAME
> using default serverNAME1 NAME2 - as above, but use NAME2 as
> serverhelp or ?   - print info on common commandsset
> OPTION  - set an optionall - print
> options, current server and host[no]debug   - print
> debugging information[no]d2  - print exhaustive
> debugging information[no]defname - append domain
> name to each query[no]recurse - ask for recursive
> answer to query[no]search  - use domain search
> list[no]vc  - always use a virtual circuit
> domain=NAME - set default domain name to NAME
> srchlist=N1[/N2/.../N6] - set domain to N1 and search list to
> N1,N2, etc.root=NAME   - set root server to NAME
> retry=X - set number of retries to X
> timeout=X   - set initial time-out interval to X
> secondstype=X  - set query type (ex.
> A,,A+,ANY,CNAME,MX,NS,PTR,SOA,SRV)
> querytype=X - same as typeclass=X - set
> query class (ex. IN (Internet), ANY)[no]msxfr   -
> use MS fast zone transferixfrver=X   - current
> version to use in IXFR transfer requestserver NAME - set
> default server to NAME, using current default serverlserver
> NAME- set default server to NAME, using initial
> serverroot- set current default server to the rootls
> [opt] DOMAIN [> FILE] - list addresses in DOMAIN (optional:
> output to FILE)-a  -  list canonical names and
> aliases-d  -  list all records-t TYPE -
> list records of the given RFC record type (ex. A,CNAME,MX,NS,PTR
> etc.)view FILE   - sort an 'ls' output file and view it
> with pgexit- exit the program
>
> -
> Scott Doctor
> sc...@scottdoctor.com
> -
>
> On 6/27/2018 12:24, Richard Hipp wrote:
>
> > If anybody can suggest patches that will get this routine
> > (https://fossil-scm.org/fossil/info/5e083abf6?ln=47) to compile and
> > work on windows, that would really be helpful.  Thanks.
> >
> >
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] ETags related build error on fossil trunk

[Antoine Chavasse]

It doesn't work.

It seems to me that the current trunk version of dispatch.c, where the
CmdOrPage struct appears to be defined (according to grep), doesn't contain
a field called "eType".

http://fossil-scm.org/index.html/artifact?name=15e80d7d8df0f698=32-37

On Sat, Feb 24, 2018 at 1:02 PM Richard Hipp <d...@sqlite.org> wrote:

> On 2/24/18, Antoine Chavasse <a.chava...@gmail.com> wrote:
> > Hello,
> >
> > I have the current build error on trunk:
>
> Might be a makefile dependency problem.  Try running "make clean
> fossil".  Report back whether or not that works.
>
> >
> > ../fossil-src/src/main.c:1770:18: warning: implicit declaration of
> > function 'CMDFLAG_TO_ETAG' is invalid in C99
> > [-Wimplicit-function-declaration]
> >etag_require(CMDFLAG_TO_ETAG(pCmd->eType));
> > ^
> > ../fossil-src/src/main.c:1770:40: error: no member named 'eType' in
> > 'struct CmdOrPage'
> >etag_require(CMDFLAG_TO_ETAG(pCmd->eType));
> >   ^
> >
> > It looks like those two errors are caused by missing changes that are
> > supposed to be in dispatch.c (the CmdOrPage struct is defined there,
> > and copying the CMDFLAG_TO_ETAG there from mkindex.c removes the
> > warning as well), but were somehow not included in any of the etags
> > branch commits.
> > ___
> > fossil-users mailing list
> > fossil-users@lists.fossil-scm.org
> > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> >
>
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] ETags related build error on fossil trunk

[Antoine Chavasse]

Hello,

I have the current build error on trunk:

../fossil-src/src/main.c:1770:18: warning: implicit declaration of
function 'CMDFLAG_TO_ETAG' is invalid in C99
[-Wimplicit-function-declaration]
   etag_require(CMDFLAG_TO_ETAG(pCmd->eType));
^
../fossil-src/src/main.c:1770:40: error: no member named 'eType' in
'struct CmdOrPage'
   etag_require(CMDFLAG_TO_ETAG(pCmd->eType));
  ^

It looks like those two errors are caused by missing changes that are
supposed to be in dispatch.c (the CmdOrPage struct is defined there,
and copying the CMDFLAG_TO_ETAG there from mkindex.c removes the
warning as well), but were somehow not included in any of the etags
branch commits.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] New "Ardoise" skin

[Antoine Chavasse]

I commited a new version  of the skin that fixes this as well as a few
other issues (wysiwyg  editor, non commit events in the timeline, and a few
other tidbits).

On Fri, Jan 12, 2018 at 3:58 PM Richard Hipp  wrote:

> The search results don't seem quite right.  The matching text is shown
> in a black font.  Example:
>
>  https://www.fossil-scm.org/skins/ardoise/search?s=utime=c
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] New "Ardoise" skin

[Antoine Chavasse]

Thanks, I fixed this. I haven't committed yet because I have discovered a
few other things not working well with the skin.

On Fri, Jan 12, 2018 at 3:58 PM Richard Hipp  wrote:

> The search results don't seem quite right.  The matching text is shown
> in a black font.  Example:
>
>  https://www.fossil-scm.org/skins/ardoise/search?s=utime=c
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] New "Ardoise" skin

[Antoine Chavasse]

I have commited a new version in the ardoise skin branch where I have
reskinned the ticket view, which fixes the overly bright fields there.

I also switched to black text on the ticket report view, so that it is
readable with the default colors.

On Wed, Jan 10, 2018 at 12:48 AM jungle Boogie <jungleboog...@gmail.com>
wrote:

> On 8 January 2018 at 04:27, Richard Hipp <d...@sqlite.org> wrote:
> > On 1/8/18, Antoine Chavasse <a.chava...@gmail.com> wrote:
> >> I'm not sure I can fix this from the skin, since the background color
> for
> >> ticket reports are configured by the user in the settings.
> >>
> >
> > I might need to enhance Fossil to recognize this situation and make
> > automatic adjustments to the background color.
> >
>
> If it's not already obvious, the fields on the ticket page are also too
> bright:
> https://www.fossil-scm.org/skins/ardoise/tktview?name=c541b6e734
>
> Thanks for the new skin, Antoine! I appreciate the work.
>
> > --
> > D. Richard Hipp
> > d...@sqlite.org
>
> --
> ---
> inum: 883510009027723
> sip: jungleboo...@sip2sip.info
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] New "Ardoise" skin

[Antoine Chavasse]

Ah, I'll have a look at this.

On Wed, Jan 10, 2018, 00:48 jungle Boogie <jungleboog...@gmail.com> wrote:

> On 8 January 2018 at 04:27, Richard Hipp <d...@sqlite.org> wrote:
> > On 1/8/18, Antoine Chavasse <a.chava...@gmail.com> wrote:
> >> I'm not sure I can fix this from the skin, since the background color
> for
> >> ticket reports are configured by the user in the settings.
> >>
> >
> > I might need to enhance Fossil to recognize this situation and make
> > automatic adjustments to the background color.
> >
>
> If it's not already obvious, the fields on the ticket page are also too
> bright:
> https://www.fossil-scm.org/skins/ardoise/tktview?name=c541b6e734
>
> Thanks for the new skin, Antoine! I appreciate the work.
>
> > --
> > D. Richard Hipp
> > d...@sqlite.org
>
> --
> ---
> inum: 883510009027723
> sip: jungleboo...@sip2sip.info
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] New "Ardoise" skin

[Antoine Chavasse]

Here's an attempt at making diffs more readable.

Since I don't have a place to host a public fossil repo with a recent
enough version of fossil, here are comparison screenshots:

Before: https://i.imgur.com/3CjqLY5.png
After: https://i.imgur.com/AFN8rBw.png

Note that I had to widen the skin somewhat to have more room for the diff
view, but it seems to look alright. I know some people even prefer skins
with a full width anyway - as a side note you can tweak the width or unlock
it by editing or removing the line "max-width: 1200px;" from the css.

I have submitted this tweak on the ardoise-skin branch.


On Mon, Jan 8, 2018 at 12:08 AM Antoine Chavasse <a.chava...@gmail.com>
wrote:

> Hi,
>
> Thanks for the feedback!
>
> I agree that the diff view could use some improvement. I'll experiment
> tomorrow with increasing the font size and darkening the background colors
> a little.
>
> On Sun, Jan 7, 2018 at 11:36 PM <sky5w...@gmail.com> wrote:
>
>> Yeah, could be old guy eyes and smallish font. But, it is low strain
>> overall.
>>
>> On Sun, Jan 7, 2018 at 5:28 PM, Jacob MacDonald <jaccar...@gmail.com>
>> wrote:
>>
>>> Interesting, I don't notice any contrast issues on my monitor. The font
>>> in diffs could be a little bigger but the black on green being a problem
>>> isn't something I picked up on.
>>>
>>> On Sun, Jan 7, 2018 at 4:16 PM <sky5w...@gmail.com> wrote:
>>>
>>>> Very nice Timeline, but super dark when browsing diff's?
>>>> The green background needs to be lighter or the font needs brightening.
>>>>
>>>> On Sun, Jan 7, 2018 at 4:51 PM, Jacob MacDonald <jaccar...@gmail.com>
>>>> wrote:
>>>>
>>>>> Wow that's a slick skin. Antoine, if you're on the list, top notch
>>>>> work. Can't wait to get it running in my repos.
>>>>>
>>>>> On Sun, Jan 7, 2018 at 3:43 PM Richard Hipp <d...@sqlite.org> wrote:
>>>>>
>>>>>> The Ardoise skin by Antoine Chavasse is now available on trunk.  You
>>>>>> can take a test-drive at
>>>>>> https://www.fossil-scm.org/skins/ardoise/timeline
>>>>>>
>>>>>> --
>>>>>> D. Richard Hipp
>>>>>> d...@sqlite.org
>>>>>> ___
>>>>>> fossil-users mailing list
>>>>>> fossil-users@lists.fossil-scm.org
>>>>>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>>>>>
>>>>>
>>>>> ___
>>>>> fossil-users mailing list
>>>>> fossil-users@lists.fossil-scm.org
>>>>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>>>>
>>>>>
>>>> ___
>>>> fossil-users mailing list
>>>> fossil-users@lists.fossil-scm.org
>>>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>>>
>>>
>>> ___
>>> fossil-users mailing list
>>> fossil-users@lists.fossil-scm.org
>>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>>
>>>
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] New "Ardoise" skin

[Antoine Chavasse]

I'm not sure I can fix this from the skin, since the background color for
ticket reports are configured by the user in the settings.

Perhaps there is a way in css to darken the colors that are set in the
elements attributes? I am not a css expert, and haven't found a way to do
this.

On Mon, Jan 8, 2018, 03:23 gumblex <gumb...@aosc.io> wrote:

> The background of the table in the "tickets" page is too light.
>
> https://www.fossil-scm.org/skins/ardoise/rptview?rn=1
>
> 2018年1月8日 07:08，Antoine Chavasse <a.chava...@gmail.com>寫道：
>
> Hi,
>
> Thanks for the feedback!
>
> I agree that the diff view could use some improvement. I'll experiment
> tomorrow with increasing the font size and darkening the background colors
> a little.
>
> On Sun, Jan 7, 2018 at 11:36 PM <sky5w...@gmail.com> wrote:
>
> Yeah, could be old guy eyes and smallish font. But, it is low strain
> overall.
>
> On Sun, Jan 7, 2018 at 5:28 PM, Jacob MacDonald <jaccar...@gmail.com>
> wrote:
>
> Interesting, I don't notice any contrast issues on my monitor. The font in
> diffs could be a little bigger but the black on green being a problem isn't
> something I picked up on.
>
> On Sun, Jan 7, 2018 at 4:16 PM <sky5w...@gmail.com> wrote:
>
> Very nice Timeline, but super dark when browsing diff's?
> The green background needs to be lighter or the font needs brightening.
>
> On Sun, Jan 7, 2018 at 4:51 PM, Jacob MacDonald <jaccar...@gmail.com>
> wrote:
>
> Wow that's a slick skin. Antoine, if you're on the list, top notch work.
> Can't wait to get it running in my repos.
>
> On Sun, Jan 7, 2018 at 3:43 PM Richard Hipp <d...@sqlite.org> wrote:
>
> The Ardoise skin by Antoine Chavasse is now available on trunk.  You
> can take a test-drive at
> https://www.fossil-scm.org/skins/ardoise/timeline
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] New "Ardoise" skin

[Antoine Chavasse]

Hi,

Thanks for the feedback!

I agree that the diff view could use some improvement. I'll experiment
tomorrow with increasing the font size and darkening the background colors
a little.

On Sun, Jan 7, 2018 at 11:36 PM <sky5w...@gmail.com> wrote:

> Yeah, could be old guy eyes and smallish font. But, it is low strain
> overall.
>
> On Sun, Jan 7, 2018 at 5:28 PM, Jacob MacDonald <jaccar...@gmail.com>
> wrote:
>
>> Interesting, I don't notice any contrast issues on my monitor. The font
>> in diffs could be a little bigger but the black on green being a problem
>> isn't something I picked up on.
>>
>> On Sun, Jan 7, 2018 at 4:16 PM <sky5w...@gmail.com> wrote:
>>
>>> Very nice Timeline, but super dark when browsing diff's?
>>> The green background needs to be lighter or the font needs brightening.
>>>
>>> On Sun, Jan 7, 2018 at 4:51 PM, Jacob MacDonald <jaccar...@gmail.com>
>>> wrote:
>>>
>>>> Wow that's a slick skin. Antoine, if you're on the list, top notch
>>>> work. Can't wait to get it running in my repos.
>>>>
>>>> On Sun, Jan 7, 2018 at 3:43 PM Richard Hipp <d...@sqlite.org> wrote:
>>>>
>>>>> The Ardoise skin by Antoine Chavasse is now available on trunk.  You
>>>>> can take a test-drive at
>>>>> https://www.fossil-scm.org/skins/ardoise/timeline
>>>>>
>>>>> --
>>>>> D. Richard Hipp
>>>>> d...@sqlite.org
>>>>> ___
>>>>> fossil-users mailing list
>>>>> fossil-users@lists.fossil-scm.org
>>>>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>>>>
>>>>
>>>> ___
>>>> fossil-users mailing list
>>>> fossil-users@lists.fossil-scm.org
>>>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>>>
>>>>
>>> ___
>>> fossil-users mailing list
>>> fossil-users@lists.fossil-scm.org
>>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>>
>>
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] New skin for trunk fossil

[Antoine Chavasse]

Thanks, and I'll be happy to do it!
I've already made sure that all the included code is either from Blitz,
which I think should be ok to reuse in this context, or from MIT licensed
code. I think the MIT code should be ok to use, since it's the skeleton css
framework, which Blitz also uses.

The remaining bits, including the file browser icons, were made by myself.

On Fri, Dec 22, 2017 at 1:40 AM Richard Hipp <d...@sqlite.org> wrote:

> On 12/21/17, Antoine Chavasse <a.chava...@gmail.com> wrote:
> > I made a new skin...
>
> The screen shots look good.  Would you be willing to secure clear
> copyright on all of the code, then sign a contributors agreement
> (https://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.html)
> so that I can incorporate your new sink into Fossil as one of the
> built-ins?
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] New skin for trunk fossil

[Antoine Chavasse]

I made a new skin, very loosely based on blitz. Basically, I wanted to make
a dark version of it and then went into a crusade against lines and border
everywhere.

One caveat is that it only works on trunk fossil for now, as it relies on
the automatic generating of the html header, and on the new element classes
that have been added recently.

Since the theme doesn't work on the version of fossil that chisel is
currently running, I've included screenshots.

http://chiselapp.com/user/achavasse/repository/ardoise-skin

There is probably room for improvement, especially since I'm a absolute CSS
newbie. Any suggestion or fix is welcome!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Veracity Version control

[Antoine Chavasse]

I'd say that his problem is to use a DVCS with lots of data in binary files
(game assets). He's bound to run into trouble even with mercurial.

The idea of keeping everything is seducing and works extremely well for
source code because it's small and is easily deltaized and compressed,
but it's just not practical for large amounts of binary data.

Where I work (on some big open world game), we don't even store very
revision of binary files, only a dozen or so, and the older ones are
discarded. Our VCS is perforce, it allows to setup this kind of rule per
file type so we can say things such as only keep 10 revisions of png
files. The metadata for all revisions are kept, but the data itself is
thrown away.

On Tue, Mar 10, 2015 at 9:52 PM Ron W ronw.m...@gmail.com wrote:

 On Tue, Mar 10, 2015 at 4:37 PM, jungle Boogie jungleboog...@gmail.com
 wrote:

 On 10 March 2015 at 12:15, Ron W ronw.m...@gmail.com wrote:

  Seems to me that he doesn't realize that Fossil separates the repository
  from the working copy. He's expecting fossil clone to work like Git
 or
  Hg where the working copy is automatically created.

 Yes, exactly. It's a couple extra steps to open it up. If he's willing
 to leave Fossil because of that, oh well!


  I suspect the main reason was the problem with large files, whatever his
 threshold for large is. Not a limit I've run into, yet.

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Problem with the output of fossile export after v1.19

[Antoine Chavasse]

I have the same issue with one of my repo and I used bisect to
pinpoint it to this commit:

http://fossil-scm.org/index.html/info/bc8d368b66053450c7f323b4e479fb5b4a878684

I don't know how the git export works though, so no idea how to fix this.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Problem with the output of fossile export after v1.19

[Antoine Chavasse]

On Wed, Jan 25, 2012 at 12:28 PM, Joerg Sonnenberger
jo...@britannica.bec.de wrote:

 I'm running with this on very large repositories. Did you do rebuilds
 after that?

Yes, I did a rebuild on my test repo after building each revision.

 There have been a number of bugs in the manifest parser that
 could break this.

Perhaps there is something in a manifest in my repo that it doesn't like.
It is that repo (which is rather small)
http://chiselapp.com/user/achavasse/repository/nea/

I'll try to have a closer look at this at home tonight.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Post-commit hook

[Antoine Chavasse]

Sorry for the email necromancy, but since there are talks about post
commit hooks again and as it seems it would generally be a useful
feature, I remembered about the roadblock that Richard encountered
that hadn't received a good anwser as far as I remember:

On Mon, Jan 3, 2011 at 12:58 PM, Richard Hipp d...@sqlite.org wrote:

 I've got a  plan for a better way to do various hooks, but in order for it
 to work cross-platform, I need code that will start a background process on
 windows.  By background process, I mean a process that will continue
 running even after its parent process exits or is killed.  If any windows
 experts out there can explain to me how to do that, or provide sample code,
 that will expedite getting the hook logic into the Fossil trunk.

So I looked into the win32 process creation APIs and played with them
on a windows box. It turns out that CreateProcess
(http://msdn.microsoft.com/en-us/library/ms682425%28v=vs.85%29.aspx)
offers a range of options to run a process in a different console
window, without a console, or with its stdin / stdout bound to
arbitrary handles.

If you look in the creation flags you can pass to CreateProcess
(http://msdn.microsoft.com/en-us/library/ms684863(v=vs.85).aspx ), you
can give CREATE_NEW_CONSOLE to create a new console window for the new
process, CREATE_NO_WINDOW to have no window created for it, or
DETACH_PROCESS to just detach the process (which seems different than
CREATE_NO_WINDOW, I think it's for the case where you want to provide
your own file handle for stdin and stdout, which I didn't try).

Those three flags are mutually exclusive.

Below is a quick test program I made that launch the file you give it
on the command line. I used a small .bat file echoing things in a loop
in both the console and a file for testing that I launched with it.

With flags set at zero, predictably the script stopped running when I
closed the console (but kept running after the program ended).

With CREATE_NEW_CONSOLE, it ran in a new, separate console window
that kept running even when the original console was closed.

With CREATE_NO_WINDOW, it ran silently (the file kept growing) and
kept running after closing the console (I had to kill it through the
task manager).

With DETACHED_PROCESS, nothing happened. Obviously the script simply
couldn't run without any form of input/output, but I suspect this is
the option to use when you want to provide your own file handles to
redirect stdin and stdout for the new process (in the STARTUPINFO
structure).


#include stdafx.h

int _tmain(int argc, _TCHAR* argv[])
{
//ShellExecute( NULL, open, argv[1], NULL, NULL, 0 );
STARTUPINFO si;
PROCESS_INFORMATION pi;

ZeroMemory( si, sizeof(si) );
si.cb = sizeof(si);
ZeroMemory( pi, sizeof(pi) );

CreateProcess( NULL,   // No module name (use command line)
argv[1],// Command line
NULL,   // Process handle not inheritable
NULL,   // Thread handle not inheritable
FALSE,  // Set handle inheritance to FALSE
CREATE_NO_WINDOW,  // No creation flags
NULL,   // Use parent's environment block
NULL,   // Use parent's starting directory
si,// Pointer to STARTUPINFO structure
pi );   // Pointer to PROCESS_INFORMATION structure

return 0;
}
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Building fossil on Windows with MinGW - dependency on libz

[Antoine Chavasse]

On Fri, Mar 18, 2011 at 12:53 PM, Arjen Markus arjen.mar...@deltares.nl wrote:

 As Mark suggests, forcing a link against static libraries seems the way
 to go.

That's how I build fossil in windows. I had the same problem and just
modified the mingw makefile to add -static in the LIB variable. I
think it would make sense to have it as default, unless there is
really a good reason to want to use zlib as a dll.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] git equivalent commands

[Antoine Chavasse]

On Fri, Mar 11, 2011 at 2:01 PM, Twylite twyl...@crypt.co.za wrote:
 On 09:59 PM, a.chava...@gmail.com wrote:

 Another option that fossil offers is to move an unwanted commit away
 to a new different branch after the fact (that you'd typically name
 mistake), which provides the equivalent functionality of a rollback
 except for the fact that it is still visible in the history.

 That sounds really useful ... how do you do it?

Use the web interface to edit the commit, check make this commit the
start of a branch, and set the branch name.

You also want to check the leaf closure box too since if it's a
mistake commit that you're getting out of the way you probably don't
want to commit anything else on that branch.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users