From: David Turner <dturner@twopensource.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git@vger.kernel.org, David Turner <dturner@twitter.com>
Subject: Re: [PATCH v2] log: add log.follow config option
Date: Tue, 07 Jul 2015 18:11:46 -0400 [thread overview]
Message-ID: <1436307106.5521.7.camel@twopensource.com> (raw)
In-Reply-To: <vpqlherlk4j.fsf@anie.imag.fr>
On Tue, 2015-07-07 at 23:42 +0200, Matthieu Moy wrote:
> Hi,
>
> Thanks for your patch. Below are some comments. Some of them are just me
> thinking out loudly (don't take it badly if I'm being negative), some
> are more serious, but all are fixable.
Thanks for the feedback!
> David Turner <dturner@twopensource.com> writes:
>
> > From: David Turner <dturner@twitter.com>
>
> If you configure your commiter id and your From field to the same value,
> you can avoid this distracting "From:" header.
>
> You're lacking a Signed-off-by trailer.
Oops. Cherry-picked over from internal repo. Will fix.
<snip> (suggestions applied)
> > + git log --name-status --pretty="format:%s" path1 > current'
>
> Whitespace: here an elsewhere, you have two spaces before path1, and we
> usually stick the > to the filename like >current.
>
> > --- a/t/t4206-log-follow-harder-copies.sh
> > +++ b/t/t4206-log-follow-harder-copies.sh
> > @@ -53,4 +53,39 @@ test_expect_success \
> > 'validate the output.' \
> > 'compare_diff_patch current expected'
> >
> > +test_expect_success \
> > + 'git config log.follow works like --follow' \
> > + 'test_config log.follow true &&
> > + git log --name-status --pretty="format:%s" path1 > current'
> > +
> > +test_expect_success \
> > + 'validate the output.' \
> > + 'compare_diff_patch current expected'
>
> I would squash these two tests. As-is, the first one doesn't really test
> anything (well, just that git log doesn't crash with log.follow).
>
> I think you meant test_cmp, not compare_diff_patch, as you don't need
> the "similarity index" and "index ..." filtering that compare_diff_patch
> does before test_cmp.
>
> That said, I see that you are mimicking surrounding code, which is a
> good thing for consistancy. I think the best would be to write tests in
> t4202-log.sh, which already tests the --follow option, and uses a more
> modern coding style which you can mimick.
> t4206-log-follow-harder-copies.sh is really about finding copies in
> --follow. Another option is to start your series with a patch like
> "t4206: modernize style".
I'm going to move over to t4202. My next re-roll will include fixes for
everything you raised.
next prev parent reply other threads:[~2015-07-07 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 18:40 [PATCH v2] log: add log.follow config option David Turner
2015-07-07 21:42 ` Matthieu Moy
2015-07-07 22:11 ` David Turner [this message]
2015-07-07 22:13 ` Junio C Hamano
2015-07-08 1:28 ` David Turner
2015-07-08 4:12 ` Junio C Hamano
2015-07-08 16:49 ` Junio C Hamano
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=1436307106.5521.7.camel@twopensource.com \
--to=dturner@twopensource.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=dturner@twitter.com \
--cc=git@vger.kernel.org \
/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 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 NNTP newsgroup(s).