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

Re: [PATCH] HACKING: More language clean-up

From: Michael W Thelen <thelenm_at_cs.utah.edu>
Date: 2004-10-14 09:06:03 CEST

Chris Pepper wrote:
>>> Thanks for the patch. I've filed it as issue #2097:
>>> http://subversion.tigris.org/issues/show_bug.cgi?id=2097
> I've cast a vote for it.
> "No responses on the dev list." on that page confuses me a bit, as
> both Julian and Michael have responded to the list...

At the time I filed the patch issue, no one had responded. :-)

> So how should I continue with language patches? Post them to this
> list, and if there are no major concerns, they go it (possibly with
> tweaking), while patches with stronger reservations become issues?

Yep, keep posting them to the list. If a patch goes for too long
without a response (or with mixed responses), I'll file it as an issue
so it's not forgotten.

> This is a little awkward, as I'd like to provide unrelated patches
> to the same files; maintaining multiple patches against the same file(s)
> is hard to keep track of. I guess I'll have to learn about branches, but
> not this week...

It can get a little hard to keep track of, but usually unrelated patches
don't touch the same parts of a file, so applying them separately (even
out of order) isn't too big a deal. If you're making unrelated changes,
you'll want to do them one at a time. Make one set of changes, create
the patch with "svn diff", then revert your changes, wash, rinse, repeat.

Michael W Thelen
It is a mistake to think you can solve any major problems just with
potatoes.       -- Douglas Adams

Received on Thu Oct 14 09:10:24 2004

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.