Gregory Stark napsal(a):
> "Zdenek Kotala" <Zdenek.Kotala@Sun.COM> writes:
>
>> Gregory Stark napsal(a):
>>> "Josh Berkus" <josh@agliodbs.com> writes:
>>>
>>>> How about hacking together a simple patch tracker instead, as Bruce
>>>> suggested? I've never found e-mail to be a particularly good way to track
>>>> patches.
>>> The thing is that we don't just want to "track" patches. We want to talk about
>>> patches.
>> I think we want to have both. If you have big patch you don't want go through
>> all patch again and again when new version is released with only few changes.
>> If you are able to have diff between two patch versions you are able preform
>> easy check if all comments are already fixed.
>
> Ah, that's not something a patch tracker or a mailing list would solve. There
> is a tool that would solve this -- a revision control system.
OK. I little bit confused what patch tracer should do. Is it only for tracking
discuss about patches?
> We aren't using CVS the way it's really intended. If all this development
> happened on branches then people could go look at the current version at any
> point, not just when authors decide to announce it. And people could generate
> diffs between the last time they looked at that branch and now etc.
Yeah, I discussed this with Peter E. during his Prague visit and it should be
big deal for code reviewing and new feature development.
Zdenek
