On Wed, 2012-05-09 at 22:18 -0500, Daniel Bankston wrote:
> Thank you, Markus and Kohei. I intend to follow the
> smaller-buildable-easier-to-read-commits-with-a-specific-purpose
> guideline. :-)
Cool - and, of course - people like to read the git commits list as
well, so in a way (d
Thank you, Markus and Kohei. I intend to follow the
smaller-buildable-easier-to-read-commits-with-a-specific-purpose
guideline. :-) I will push a small commit soon that will serve a dual
purpose of being my first commit toward the goals of the GSOC Cal
performance improvements project and of
Hi Daniel,
On Wed, May 9, 2012 at 7:36 PM, Daniel Bankston
wrote:
> Hi, Kohei and Markus,
>
> I understand that when dealing with the master branch, a contributing
> developer is supposed to send a patch to the mailing list with the subject
> prefixed with [PATCH]. What process should I follow w
Hello Daniel,
> I understand that when dealing with the master branch, a contributing
> developer is supposed to send a patch to the mailing list with the subject
> prefixed with [PATCH]. What process should I follow when pushing to the
> feature/gsoc-calc-perf branch? Should I notify you in so
