On Tue, Aug 30, 2016 at 10:10 PM, John Found wrote:
> Well, my exact opinion is that as long as most web servers allow it, there
> is nothing wrong in compression the data by the CGI script. But IMHO, such
> behavior is half step beyond the CGI specification and can be qualified as
> a "common pr
On 08/30/2016 02:31 PM, Richard Hipp wrote:
> A new feature of Fossil (currently unreleased and only available to
> people who are willing to recompile the code on trunk) is "unversioned
> files".
>
> https://www.fossil-scm.org/fossil/doc/trunk/www/unvers.wiki
Hey, cool. This seems like a mov
kamloops$ fossil unver revert
assertion "uvStatus==2" failed: file "./src/xfer.c", line 1893,
function "client_sync"
[1] Abort trap (core dumped) fossil unver revert
kamloops$
On 8/30/16, bch wrote:
> On 8/30/16, sky5w...@gmail.com wrote:
>> This is a welcome addition to house nuisance files
On 8/30/16, sky5w...@gmail.com wrote:
> This is a welcome addition to house nuisance files like bitmaps, icons,
> etc.
> But, I am confused by the in-out nomenclature?
>
> Push to remote: fossil unversioned sync
> Pull from remote: fossil unversioned revert
> Checkout unv files: fossil unver
This is a welcome addition to house nuisance files like bitmaps, icons, etc.
But, I am confused by the in-out nomenclature?
Push to remote: fossil unversioned sync
Pull from remote: fossil unversioned revert
Checkout unv files: fossil unversioned export FILE //1 at a time?
If we have the p
On 8/30/2016 1:55 PM, Ron W wrote:
Why only "sync -u" ?
Probably to give an easy way to distinguish developer's clones from full
mirrors. If the unversioned files are built releases, then I don't need
them on my dev machine, so no reason to sync them.
If unversioned files are used for somet
Why only "sync -u" ?
On Tue, Aug 30, 2016 at 2:31 PM, Richard Hipp wrote:
> A new feature of Fossil (currently unreleased and only available to
> people who are willing to recompile the code on trunk) is "unversioned
> files".
>
> https://www.fossil-scm.org/fossil/doc/trunk/www/unvers.wiki
>
On Tue, 30 Aug 2016 12:47:07 -0600
Warren Young wrote:
> On Aug 29, 2016, at 11:09 PM, John Found wrote:
> >
> >>> IMHO, the cgi script should not return "Content-Encoding” header
> >>
> >> Of course it should. Only the data source knows what content encoding it
> >> used. fcgiwrap and your
On Aug 29, 2016, at 11:09 PM, John Found wrote:
>
>>> IMHO, the cgi script should not return "Content-Encoding” header
>>
>> Of course it should. Only the data source knows what content encoding it
>> used. fcgiwrap and your “experimental” web server should just pass that
>> header along, sin
A new feature of Fossil (currently unreleased and only available to
people who are willing to recompile the code on trunk) is "unversioned
files".
https://www.fossil-scm.org/fossil/doc/trunk/www/unvers.wiki
The "Download" page on the canonical Fossil website is now implemented
using these unv
Hi,
I think there is a typo in the "fossil help push" command:
Use the
"configuration *pull*" command to push website configuration details.
should be
Use the
"configuration *push*" command to push website configuration details.
Tiny patch attached.
Best Regards,
Johan
--- sync.c2016-08-
11 matches
Mail list logo
