With all this talk about how to keep draft work out of the repo when done with
it, I started playing with the various methods mentioned.
I noticed the following, and I would like to know if this expected behavior or
some bug.
Regardless, it is disturbing to lose trunk (or other branch) commits
On 12/17/2015 11:45 PM, Stephan Beal wrote:
On Thu, Dec 17, 2015 at 9:28 PM, Ross Berteig > wrote:
Build fossil with JSON support, then you get access to a bunch of
features with data transported in JSON with suitable quoting. I'm
Tony Papadimitriou wrote:
With all this talk about how to keep draft work out of the repo when
done with it, I started playing with the various methods mentioned.
I noticed the following, and I would like to know if this expected
behavior or some bug.
The following is only tangentially related
i would be tickled pink to see you take that on :). i am more than happy to
help/support in any way, just can't currently commit (no pun intended) to
more than moderate amounts of typing, as my arm just can't do it. (That
doesn't rule out Skype or similar, though.)
- stephan
Sent from a
4 matches
Mail list logo