James Denholm wrote:
> Felipe Contreras <felipe.contre...@gmail.com> wrote:
> > James Denholm wrote:
> >> It's not anybody else's job to take your patches and drizzle them in the
> >> honey of respectable discourse.
> >
> > It's nobody's job to do anything. This a collaborative effort and in a
> > collaborative effort everbody chimes in to do different things.
> No, true, but my point was more related to that it's ones own "task",

It's still the same thing. Nobody gets assigned any tasks; people choose their
own tasks, and they might choose tasks that other people were doing.

> > It's not Jeff's patches, they are our patches, they are part of the project.
> > And it's not unusual for multiple people working on a patch series; 
> > oneperson
> > doing most of the work, another adding tests, another cleaning 
> > updocumentation.
> > It's also no unheard of from a person picking up a patch series somebody 
> > else
> > stopped working on.
> This, of course, would be the _other_ case where a proposal's
> merits are already known and accepted by the community.

No. John might have sent a patch series X, and maybe he didn't explain
correctly how it would benefit the project. Later on Mark finds out how those
patches would be useful for himself and takes upon himself to get them merged,
so he cleans them up and send an updated version with a clear explanation of
how they would be useful.

It's still the same proposal X, but a different person and a different strategy
to get them merged.

In other words, the fact that the community has not yet accepted the merits of
an approach doesn't mean that another person cannot champion it.

> The default may be wrong, you and I might agree that the default is
> wrong, Junio and Torvalds and RMS and The Queen of England
> might all agree that the default is wrong... But if we all live across
> from a bread shop, it's going to be a difficult task for you to convince
> us to go hunting.

It doesn't matter if you want to go hunting and I want to buy bread, either one
of those is better than starving to death.

In the Git project though, we choose to starve to death. Neither were my
patches picked, nor did anybody else step up with a different proposal, we just
did nothing, which is what we always do.

Felipe Contreras
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to