Subject: Re: [boost] [git] automatic ticket closing
From: Cox, Michael (mhcox_at_[hidden])
Date: 2013-12-05 18:34:52
On Thu, Dec 5, 2013 at 9:28 AM, Steven Watanabe <watanabesj_at_[hidden]>wrote:
> On 12/05/2013 01:00 AM, Bjorn Reese wrote:
> > On 12/05/2013 12:53 AM, Beman Dawes wrote:
> >> I think the same thing is happening as happened with Git itself. You can
> >> speculate about whether A is better than B all you want, but actually
> >> using
> >> something alters your perspective. If I had to put my finger on what
> >> is was
> >> in the case of the issues lists, I would say the responsiveness of the
> >> GitHub issue tracker. But whatever it is, something is making me want to
> >> abandon the old trac issue tracker ASAP.
> > Please notice that the GitHub issue tracker does not allow you to attach
> > patches (you can only attach graphics.)
> Patches aren't the only use for attachments. Test
> cases are also common (and absolutely critical). If
> the github issue tracker doesn't support attachments,
> then it's simply a non-starter.
I'm assuming by the term test cases that means Boost.Test unit-tests.
Wouldn't be more convenient to see the modified/new unit-tests for a
library code change in the pull-request?
> > This raises the question if the only way to contribute will be through
> > GitHub pull requests. While these certainly are convenient to the
> > maintainers, they do require extra work for the casual contributor:
> > https://help.github.com/articles/syncing-a-fork
> In Christ,
> Steven Watanabe
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk