FINFO (Usage: fossil finfo ?OPTIONS? FILENAME) is one of the most useful
features of fossil as it accepts a filename and provides its history of changes
(unfortunately, it does not follow possible file renames, but that’s another
issue).
What I would like is to have the possibility to also spec
On Wed, Oct 15, 2014 at 4:54 PM, Ron W wrote:
> But that's just the executive summary. The details will require much
> research, planning and design.
>
After doing some research, I was reminded that SVN branches (and tags) are
implemented as copy-by-reference. This means that the definition of a
On Thu, Oct 16, 2014 at 3:14 AM, Stephan Beal wrote:
> i'm not aware of any WWW feature of fossil which uses checkout-level data
> except maybe to display versioned settings.
>
For embedded documents:
baseURL/doc/version/path
if version is "ckout", then the file in the associated working sp
I'm maintaining a large(ish) repo for production deployments of
various software like Apache httpd, OpenSSL, etc.
What I have is a [vendor] branch for the vanilla vendor software (ie:
httpd-2.2.27.tar.gz), and "feature branches" for configuration/tweaks
(ie: [redhat_build] for building for redhat
On Thu, Oct 16, 2014 at 9:14 AM, Stephan Beal wrote:
> There is no commit API for JSON.
>
Addenda: any hypothetical commit-like behaviour would be limited to text
data (specifically, UTF8), as JSON does not support binary data directly
(only via 3rd-party encodings like base64). _In theory_ (acc
On Wed, Oct 15, 2014 at 11:44 PM, Carlos Alberto Ruiz Uribe <
carlos.ru...@softtek.com> wrote:
> I would like to create a simply Web Client that will work likes the
> desktop application Fuel-scm using the JSON-API, I have reviewed the JSON
> API Documentation, and i ‘m wondering:
>
>
> How t
6 matches
Mail list logo
