Re: [PATCH 1/3] cherry-pick: add support to copy notes
- From
Felipe Contreras <felipe.contreras@gmail.com>
- Date
- May 29, 2013, 14:01 UTC
- Message-ID
- <CAMP44s3TKCtn8f_zU1geFcmgCFVkKF+ipBFkV+cSa+6CtLX0gA@mail.gmail.com>
- In-Reply-To
- <CALkWK0kK+Mbscsue0wwU5QDKXCrw5Q078MCdOVCoJnMZq7T6UA@mail.gmail.com>
On Wed, May 29, 2013 at 8:48 AM, Ramkumar Ramachandra <artagnon@gmail.com> wrote:
> Felipe Contreras wrote:
Show 11 quoted lines
>> There's nothing wrong with me choosing how best to spend my time. Really. > > Ofcourse you are. You have arguably spent it very productively > solving a lot of user issues (especially remote-bzr). > > Personally, I try to do the minimum amount of boring work required to > make sure that a good series gets in. Sometimes this is a little high > (for a recent example, see my pickaxe-doc series). The result being > that I just won't work on documentation in the future because doing > iterations is so piss boring: the git community needs to recognize > this problem and make amends.
I don't mind doing as many iterations as it takes, as long as it's about meaningful issues.
I don't particularly enjoy, but I'm OK with discussing non-meaningful issues.
What I'm not OK with is disagreements that end up breaking the communication, specially when a crystal-clear case has been made (IMO), and the patch goes to limbo for no reason. That I think is a real problem.
For this particular patch, I don't care if it goes in at the moment. I have something big on the pipeline, and I would rather drop this than loose penguin points, although I probably don't have any left.
Cheers.
-- Felipe Contreras