Hmmm. Your link distinguishes 3 cases, out-of-tree (such as
in a github bug tracker), off-branch (which appears to be what
you are suggesting, right?), and on-branch (part of the sources
in the Axiom scheme).
He raises the question of merging bugs where systems might
have custom software to do thi
On 08/06/2016 01:28 PM, Tim Daly wrote:
> Methinks I mis-understood your DAG suggestion.
>
> Are you suggesting that the source code is in one DAG
> (src/doc/build/etc) and that bugs are in a parallel DAG?
More or less yes. I think it is a bit like when you document a project
on github.
https://
Methinks I mis-understood your DAG suggestion.
Are you suggesting that the source code is in one DAG
(src/doc/build/etc) and that bugs are in a parallel DAG?
Are you also suggesting that the "bug DAG" be a git repo
separate from the source repo?
In a pile-of-sand (POS) project organized by a dir
On 08/06/2016 02:51 AM, Tim Daly wrote:
> Fixed bugs seem uninteresting. Several things failed on my car, for
> instance, that were fixed. There is rarely the need to revisit
> failures, except possibly in regression tests, like brakes :-)
I don't understand your comment. You are in favour of ev
