All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Paul-Sebastian Ungureanu <ungureanupaulsebastian@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [GSoC] A blog about 'git stash' project
Date: Sun, 6 May 2018 18:52:24 +0530	[thread overview]
Message-ID: <ef15b063-c0e3-a5e9-7418-35d2d6b954f3@gmail.com> (raw)
In-Reply-To: <67e6d306-0885-9340-13c8-3e3d4333dc20@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2371 bytes --]

Hi Sebi,

On Friday 04 May 2018 03:18 AM, Paul-Sebastian Ungureanu wrote:
> 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!


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2018-05-06 13:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 21:48 [GSoC] A blog about 'git stash' project Paul-Sebastian Ungureanu
2018-05-03 22:10 ` Johannes Schindelin
2018-05-04 21:48   ` Paul-Sebastian Ungureanu
2018-05-06 13:22 ` Kaartic Sivaraam [this message]
2018-05-07 16:37   ` Paul-Sebastian Ungureanu
2018-05-17  6:58     ` Kaartic Sivaraam
2018-05-17  7:11       ` Kaartic Sivaraam
2018-05-17  9:09         ` Johannes Schindelin
2018-05-17 10:29           ` Kaartic Sivaraam
2018-05-20 19:33             ` Paul-Sebastian Ungureanu
2018-05-23  3:20               ` Kaartic Sivaraam
2018-05-08  4:00 ` Taylor Blau
2018-05-08 21:19   ` Paul-Sebastian Ungureanu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ef15b063-c0e3-a5e9-7418-35d2d6b954f3@gmail.com \
    --to=kaartic.sivaraam@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=ungureanupaulsebastian@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.