[haiku-development] Re: Apply Clang work from midar-github.master
- From: Jonathan Schleifer <js-haiku-development@xxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 15 Dec 2013 17:14:11 +0100
Am 14.12.2013 um 13:20 schrieb Fredrik Holmqvist <fredrik.holmqvist@xxxxxxxxx>:
> I do hear some frustration
Sorry, but I can only agree here. When I was at last year's BeGeistert, it was
easy to get changes in, as there were enough people to bug IRL to commit it.
However, once I was home, I had a hard time getting something in.
This is also true for the clang branch:
I submitted several small changes which were reviewed and I got a lot of
feedback that I incorporated. After I fixed everything that was criticized,
there was no feedback anymore. I then rebased it after a few months and
converted it to one medium-sized patch (I really wouldn't call it big), so that
I can properly document it (if you look at the full commit message, you can see
it's quite long and contains a detailed explanation about how to use it). I
didn't want to create a new text file describing all that which is going to
change, so I decided to have it in the commit message. Also, splitting it into
many commits that just change 2 lines seemed wrong, as then there would have
been no way to group these commits.
However, for almost a year, nothing happened then and I moved on to other
things. The patch finally fulfilled all requirements that were given to me on
the mailing list, yet nothing happened, so I didn't pursue it any further. I
deemed that as lack of interest and moved on to other projects.
But even for small patches, it was extremely hard for me to get them in, which
is one of the main reasons I lost interest. Even for such small things as
fixing the rendering of bold text in the terminal so an m actually looks like a
letter and not like a blob.
Just my 2 cents…
--
Jonathan
Other related posts:
