git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Packham <judge.packham@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: git@vger.kernel.org, jrnieder@gmail.com, gitster@pobox.com,
	bebarino@gmail.com
Subject: Re: [PATCHv2 2/2] tests for git alternate command
Date: Thu, 25 Mar 2010 11:51:15 -0700	[thread overview]
Message-ID: <a038bef51003251151h5ede3ab8jc22a61cc35706240@mail.gmail.com> (raw)
In-Reply-To: <4BAB12E1.8070602@viscovery.net>

On Thu, Mar 25, 2010 at 12:38 AM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> Am 3/25/2010 7:07, schrieb Chris Packham:
>> Signed-off-by: Chris Packham <judge.packham@gmail.com>
>
> Your patches violate whitespace rules. Use 'git show --check' to see the
> questionable lines.
>

Will do. BTW theres no mention of --check in git show --help, but one
itch at a time.

>> ---
>> I wasn't sure about the test numbering so I just grabbed the highest one. Still
>> need to add tests for the deletion use case.
>
> According to t/README, t1* would be a suitable category, perhaps t1430.
>
>>  t/t9800-git-alternate.sh |   95 ++++++++++++++++++++++++++++++++++++++++++++++
>
> "git" in the name is redundant
>

Is t1430-alternate-cmd.sh OK with everyone?

>> +test_expect_success \
>> +     'Setup for rest of the test' '
>
> The modern style for test headers is
>

[snip]

Will incorporate in next update

>> +#rm -rf A B C D base
>> \ No newline at end of file
>
> test_done
>

Ah, I knew it would be something simple like that. I guess I should
have started by reading t/README.

  reply	other threads:[~2010-03-25 18:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22 17:26 Question about .git/objects/info/alternates Chris Packham
2010-03-23  2:42 ` Jonathan Nieder
2010-03-24 18:53   ` Chris Packham
2010-03-24 19:23     ` Jonathan Nieder
2010-03-24 19:58     ` Junio C Hamano
2010-03-24 20:35       ` Chris Packham
2010-03-25  6:07         ` Chris Packham
2010-03-25  6:07         ` [PATCHv2 1/2] Add git alternate command Chris Packham
2010-03-29  7:32           ` Junio C Hamano
2010-03-31  4:35             ` Chris Packham
2010-03-25  6:07         ` [PATCHv2 2/2] tests for " Chris Packham
2010-03-25  7:38           ` Johannes Sixt
2010-03-25 18:51             ` Chris Packham [this message]
2010-03-26  0:48               ` Miklos Vajna
2010-03-26  6:44               ` Johannes Sixt
2010-03-24 20:16     ` Question about .git/objects/info/alternates Stephen Boyd
2010-03-24 20:37       ` Chris Packham

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=a038bef51003251151h5ede3ab8jc22a61cc35706240@mail.gmail.com \
    --to=judge.packham@gmail.com \
    --cc=bebarino@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j.sixt@viscovery.net \
    --cc=jrnieder@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 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).