[wp-hackers] Switching from SVN

[Otto]

On Thu, Dec 9, 2010 at 11:21 PM, Eric Mann <eric at eam.me> wrote:
> A Git base system would allow us to retain a similar system to the one we
> have now - lots of developers can work on WordPress and submit changes but
> only a select few can commit to the central repository.  When a developer
> who's not a core contributor has a patch to submit, s/he pushes the
> changeset to a public location (not to trunk, but to a branch of the
> repository marked specifically for a ticket) and anyone else can clone from
> that branch.

Hmm.. Sorry, but it sounds complicated to me. Basically, you're saying
that I have to somehow hook my repo to yours just to test a patch.
Which means that I have to know some kind of obscure features of a
version control system to somehow hook my copy of the repo into yours
(or your branch), then do some kind of update to get your changes and
test them.

As opposed to the dirt simple process of applying a patch file.

> It makes testing a patch as simple as right-clicking in a GUI ...

Huh? I right click the diff file and select "Apply Patch". How hard is
it to apply a patch for you?

> If the patch is good and the core committers decide to make it core, they
> merge it into trunk.

So the merge load is put onto the maintainers then? I'd really rather
have the merge burden be on those submitting the patch in the first
place, where it is now.


On Thu, Dec 9, 2010 at 11:23 PM, Ankur Oberoi <aoberoi at gmail.com> wrote:
> its diff because for the individual, merging the changes that occurred in
> trunk because fast and easy, and the right person for the job is doing it
> (namely the person who knows where their code has impact and where it
> doesnt).

Err... You do an svn up and then correct the conflicts. When you're
done with the merge (refreshed patch), you submit the diff. The burden
of the merge is on the person creating the patch, where it should be.
Maintainers shouldn't be tasked with any merging at all.

-Otto