[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: The point of patch management.

From: <kfogel_at_collab.net>
Date: 2003-07-07 16:41:13 CEST

Wolf Josef <josef.wolf@siemens.com> writes:
> > And regarding (a): not all patches posted need to be recorded, at
> > least not right away. For example, you filed issue #1391 regarding
> > P. Marek's timestamp patch, but if you watch the (still active) dev
> > list thread about this, you'll see that there is no consensus on the
> > feature, let alone on this implementation of the feature. There is
> > some consensus regarding a much simpler subset of the feature; look
> > for recent posts by Ben Collins-Sussman, I don't remember the exact
> > subject but it'll be obvious. Also, see issues #1256 and #1112 (hmmm,
> > which may be dups of each other?).
> Ough! Karl, don't you feel you are expecting too much from a single
> person? The svn-dev list is a heavy-volume list. Following almost
> all threads so close that you can see whether consensus was reached
> implies that you read all the arguments very carefully.

No -- remember that it's not necessary to read all of each thread.
Instead, you save the thread starting from the patch, and then you
cherry pick messages to read (usually from around the end of the
thread). If the consensus is clear, you're done. If not, you may
have to read more.

(After all, Sander Roobol managed to do it. And I used to do it too,
so I know it's possible.)

> Often two arguments sounds the same but are really very different.
> The oposite condition also often occures: two arguments sound
> different but are really the same when you look closer on them.
> So you need a very deep technical understanding _and_ you need
> to follow discussions _very_ closesly in order to see whether a
> consensus was reached. IMHO the dev-list have too much traffic
> for a single person to follow almost all the threads _that_
> carefully.

You don't need deep understanding, nor do you need to follow
discussions very closely. You just need broad understanding, and to
follow the discussions lightly. These differences of degree are what
make the job feasible.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 7 17:32:41 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.