On 07/13/18 12:23, Warren Young wrote:
In my public Fossil projects, the policy is that any checkin that is
potentially destabilizing should be done on a branch, as should any
coherent line of work that will require multiple checkins to complete.
Trunk is ideally stable at all times, so as long
On Jul 13, 2018, at 9:39 AM, Andy Goth wrote:
>
> On 07/11/18 16:10, Warren Young wrote:
>> On Jul 10, 2018, at 8:58 PM, Andy Goth wrote:
>>> I thought it interesting that he spoke of merging as if it were a
>>> distinct task in the workflow for adding a file.
>> Did he check the file in on a
On 07/11/18 16:10, Warren Young wrote:
On Jul 10, 2018, at 8:58 PM, Andy Goth wrote:
I thought it interesting that he spoke of merging as if it were a
distinct task in the workflow for adding a file.
Did he check the file in on a branch and then merge it down to trunk?
No he did not, but
On Jul 10, 2018, at 8:58 PM, Andy Goth wrote:
>
> "Got fossil ui working. Added, merged and committed website_design.md." I
> thought it interesting that he spoke of merging as if it were a distinct task
> in the workflow for adding a file.
Did he check the file in on a branch and then
I'm working on a project with a new Fossil user. Right now it's just
the two of us. He was able to create the Fossil repository on Chiselapp
without any fuss, but since then it's been all my work, aside from his
wiki edits. Until today. Now is the first time he tried cloning the
5 matches
Mail list logo
