From: Paul-Sebastian Ungureanu <ungureanupaulsebastian@gmail.com>
To: Kaartic Sivaraam <kaartic.sivaraam@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: Mon, 7 May 2018 19:37:09 +0300 [thread overview]
Message-ID: <e8a81d38-57d7-2974-b5c7-3489e8ceb1fc@gmail.com> (raw)
In-Reply-To: <ef15b063-c0e3-a5e9-7418-35d2d6b954f3@gmail.com>
Hello,
On 06.05.2018 16:22, Kaartic Sivaraam wrote:
> 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.
Thank you a lot!
> 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).
I heard of it and used it a couple of times (for the micro-project and
some other patch).
> Sorry for the off-topic info about the tests in this mail :-)
You shouldn't be sorry. Nothing was off-topic; I found everything you
said to be helpful! Every feedback is welcomed!
> Hope you're able to achieve your goal as planned and have a great time
> during this summer of code!
Thank you one more time! I know it will be a good summer.
Best,
Paul Ungureanu
next prev parent reply other threads:[~2018-05-07 16:37 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
2018-05-07 16:37 ` Paul-Sebastian Ungureanu [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e8a81d38-57d7-2974-b5c7-3489e8ceb1fc@gmail.com \
--to=ungureanupaulsebastian@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).