Subject: Re: [boost] Respecting a projects toolchain decisions
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2011-01-01 13:02:26
On 1/1/2011 1:33 AM, Dean Michael Berris wrote:
> Right, I guess I never really had that issue as I generally want to be
> in a certain "mode" when I'm looking through issues.
> GitHub makes that really simple since I only get notifications on
> issues I'm involved in -- ones where I either commented or posted
> myself -- and then I can go look at the issues relevant to the library
> I'm working on from that library's issue tracker.
> I think this is also the reason why I don't like the Trac approach
> where all the issues just get piled up in the same container and you
> have to filter it out actively.
> Maybe it's just the way I work that's different from everyone else's
> preferred way of working on things?
From my point of view, it doesn't really matter
whether everything is in one place and I can
filter out what I'm not interested in or is separate
and I can somehow aggregate it all. I want both
but I don't really care how I get them nor how
the data is actually stored.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk