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
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
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
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
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
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
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.c
7 matches
Mail list logo