Felipe Contreras wrote:
> I am helping my fellow developers by replying to the comments they
> make when I send the patches for review. Unfortunately, the only
> developer other than you that has made any comment at all, Ramkumar
> Ramachandra, did so in a bellicose tone, but I replied to all his
> comments either way, which where invalid.
I've never wanted to pick fights with anyone, and I don't foresee
having a desire to do so in the future. I was just saying what was on
my mind, which is along the lines of: you have written this patch with
the attitude "I know what I'm doing, my users will benefit, and nobody
else is going to look at this patch anyway"; I'm worried about what
your other patches look like if this is your attitude towards
development. Junio is harping about the same thing: the impedance
mismatch between you and the rest of us.
> The history *is* readable. If anybody has any problems with the commit
> messages, the place to mention such problems is IN THE PATCH REVIEW.
> Nobody has done that, because either nobody has any problems, or they
> are not interested. Either way, there's nothing I can do about it.
That's what I've been trying to say over and over again: _why_ are
people not reviewing your patches?
0. Because nobody has any problems with them.
1. Because nobody on the git list cares about remote-hg.
2. Because you're stubborn as a mule, and the resulting thread often
results in long-winded discussions like this one (which wastes
everyone's time). Therefore, the potential reviewer's reasoning is
that their review time is better spent elsewhere, where their review
is actually appreciated.
Hint: it's not (0).
If you're claiming that (1) is the case, then why are you posting to
the git list and hitting everyone's inboxes? Maintain your project
I'm claiming that it's (2). In which case, it's you who needs changing.
> I'm willing to change my ways when there's reason to change my ways,
> and so far, nobody has provided any evidence that my commit messages
> are indeed lacking, only *opinions*.
You want a formal mathematical proof? We operate on opinions, and
freeze what we think we all agree with into "community guidelines".
> Other people are perfectly fine with them:
So you're now claiming that we're the ones at fault (Peff, Thomas,
Junio, and me, among others). Okay, so why are you forcing your
changes and opinions down our throats? You're in the wrong community:
join a community of people who are more like you (or start your own
project), and stop wasting our time.
Junio C Hamano wrote:
> I do
> not agree with Ram at all when he says that developers are more
> important than users, and I agree with you that the project exists
> for users, and not for developers.
If Peff were to suddenly stop working on git one day (because he was
frustrated with the community/ development practices), we'd all lose a
lot more than if one random end-user switches to using hg for his tiny
personal projects. I'm _not_ claiming that there's a split between
users and users that are developers (we have one mailing list for
everyone, and I like that). What I'm claiming is that we cannot (and
should not) pay equal attention to every user of git. Some users are
more important than others. Again, that does _not_ mean that we push
a change that benefits one important user but breaks everyone else's
Ofcourse the project exists for its users; we're not doing research.
However, we don't all have to write tutorials to keep in touch with
end-users who are completely detached from the development process
(our time is better spent elsewhere), or even have an
end-user-friendly bug tracker (where the SNR is very low). We don't
have to consciously reach out to people we're not connected to
directly: if we're all sufficiently connected to the real world, the
itches/ bugs worth working on will always find their way to us. We
live in a connected world.
Yes, I know. You're going to respond to this email arguing about why
you're Right and why I (and everyone else) is Wrong, either by quoting
what Linus (TM) said and twisting it to mean what you want, belaboring
over what you've already said, or something similar.
I've given up on you, and I suspect a lot of other people have too.
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