Re: [GSoC] A blog about 'git stash' project

From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Date: May 6, 2018, 13:22 UTC
Message-ID: <ef15b063-c0e3-a5e9-7418-35d2d6b954f3@gmail.com>
In-Reply-To: <67e6d306-0885-9340-13c8-3e3d4333dc20@gmail.com>

Hi Sebi,

On Friday 04 May 2018 03:18 AM, Paul-Sebastian Ungureanu wrote:

Show 11 quoted lines

> Hello everybody,
> 
> The community bonding period started. It is well known that for a
> greater rate of success, it is recommended to send weekly reports
> regarding project status. But, what would be a good form for such a
> report? I, for one, think that starting a blog is one of the best
> options because all the content will be stored in one place. Without
> further ado, I would like you to present my blog [1].
> 
> Any feedback is greatly appreciated! Thank you!
>

The blog looks pretty well written. I also read your proposal. It also seems to be pretty much well written. I like the way you explain things. Particularly, you seem to be explaining the problem and the way you're about to approach it well. The plan seems pretty good.

I just thought of suggesting one thing which might possibly be redundant. I think you're aware of the fact that the Git project has Travis-CI builds enabled[1] which you could take advantage of to ensure your changes pass in various text environments.

If you're interested in testing your changes (which I suspect you are), you might also be interested in 'git-test'[2], a tool built by Michael Haggerty. Unlike the Travis-CI tests which test only the tip of the change, 'git-test' would help you ensure that every single commit you make doesn't break the test suite (which is both a nice thing and is expected here).

Sorry for the off-topic info about the tests in this mail :-)

Hope you're able to achieve your goal as planned and have a great time during this summer of code!

References: [1]: https://github.com/git/git/blob/master/Documentation/SubmittingPatches#L70

[2]: https://github.com/mhagger/git-test

Regards, Kaartic

QUOTE:

“The most valuable person on any team is the person who makes everyone else on the team more valuable, not the person who knows the most.”

      - Joel Spolsky

KIND NOTE TO THE NATIVE ENGLISH SPEAKER:

As I'm not a native English speaker myself, there might be mistaeks in my usage of English. I apologise for any mistakes that I make.

It would be "helpful" if you take the time to point out the mistakes.

It would be "super helpful" if you could provide suggestions about how to correct those mistakes.

Thanks in advance!