This post is a testament to Fossil's design and the ease of reading its
implementation. I've also added a Fossil patch at the bottom. I humbly
hope the devs will incorporate it into the product, or tell me what is
wrong with it so I can perhaps fix it. Otherwise, I hope the community
finds it
On Sat, Sep 6, 2014 at 11:21 AM, Eric Rubin-Smith eas@gmail.com wrote:
This post is a testament to Fossil's design and the ease of reading its
implementation. I've also added a Fossil patch
[...]
It requires a little hacking of the Fossil source to expose some data to
the TH1 Transfer
Great. I'll start making the necessary tweaks to expose the UUID(s). Also,
I think
Ron W has a point about the variable naming, I think the list of UUIDs
should be named
uuids.
--
Joe Mistachkin
___
fossil-users mailing list
I think these changes should work:
https://www.fossil-scm.org/index.html/info/acb61e5ee9
Please let me know if there are any issues. Unless there are serious
objections,
I would really like to have these changes included in the upcoming 1.30
release.
--
Joe Mistachkin
Ron W wrote:
This enhancement to Fossil will certainly make integration with other
tools easier, not just Slack
I was thinking of an example: git. Right now there's a bulk import
from git, and a bulk export to git. The present feature might be used
along with git's hooks features to
5 matches
Mail list logo
