public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: "Galan Rémi" <remi.galan-alfonso@ensimag•grenoble-inp.fr>
Cc: Git List <git@vger•kernel.org>,
	Remi Lespinet <remi.lespinet@ensimag•grenoble-inp.fr>,
	Guillaume Pages <guillaume.pages@ensimag•grenoble-inp.fr>,
	Louis-Alexandre Stuber 
	<louis--alexandre.stuber@ensimag•grenoble-inp.fr>,
	Antoine Delaite <antoine.delaite@ensimag•grenoble-inp.fr>,
	Junio C Hamano <gitster@pobox•com>,
	Eric Sunshine <sunshine@sunshineco•com>
Subject: Re: [PATCH/RFCv3 1/2] git-rebase -i: add command "drop" to remove a commit
Date: Tue, 02 Jun 2015 16:17:52 +0200	[thread overview]
Message-ID: <vpqeglujisv.fsf@anie.imag.fr> (raw)
In-Reply-To: <1433252180-25591-1-git-send-email-remi.galan-alfonso@ensimag.grenoble-inp.fr> ("Galan \=\?iso-8859-1\?Q\?R\=E9mi\=22's\?\= message of "Tue, 2 Jun 2015 15:36:19 +0200")

Galan Rémi <remi.galan-alfonso@ensimag•grenoble-inp.fr> writes:

> +test_expect_success 'drop' '

Please, be more descriptive in the first argument of
test_expect_success. It's usually a good thing to say not only what the
test stresses but also what the expected behavior is.

test_expect_success 'drop actually drops the lines' '
	...
'

?

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  parent reply	other threads:[~2015-06-02 14:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02 13:36 [PATCH/RFCv3 1/2] git-rebase -i: add command "drop" to remove a commit Galan Rémi
2015-06-02 13:36 ` [PATCH/RFCv3 2/2] git rebase -i: warn about removed commits Galan Rémi
2015-06-02 14:56   ` Matthieu Moy
2015-06-02 16:32     ` Remi Galan Alfonso
2015-06-02 18:22       ` Junio C Hamano
2015-06-03  6:42       ` Matthieu Moy
2015-06-03  7:33         ` Remi Galan Alfonso
2015-06-03  8:25           ` Remi Galan Alfonso
2015-06-02 14:17 ` Matthieu Moy [this message]
2015-06-02 14:32   ` [PATCH/RFCv3 1/2] git-rebase -i: add command "drop" to remove a commit Remi Galan Alfonso

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=vpqeglujisv.fsf@anie.imag.fr \
    --to=matthieu.moy@grenoble-inp$(echo .)fr \
    --cc=antoine.delaite@ensimag$(echo .)grenoble-inp.fr \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    --cc=guillaume.pages@ensimag$(echo .)grenoble-inp.fr \
    --cc=louis--alexandre.stuber@ensimag$(echo .)grenoble-inp.fr \
    --cc=remi.galan-alfonso@ensimag$(echo .)grenoble-inp.fr \
    --cc=remi.lespinet@ensimag$(echo .)grenoble-inp.fr \
    --cc=sunshine@sunshineco$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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