public inbox for [email protected]  

help / color / mirror / Atom feed

From: Zdenek Kotala <[email protected]>
To: Gregory Stark <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: [email protected]
Subject: Re: Posting to hackers and patches lists
Date: Sat, 10 May 2008 13:39:51 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Gregory Stark napsal(a):
> "Zdenek Kotala" <[email protected]> writes:
> 
>> Gregory Stark napsal(a):
>>> "Josh Berkus" <[email protected]> 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

view thread (42+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Posting to hackers and patches lists
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox