From: "Sverre Hvammen Johansen" <hvammen@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/5] New merge tests
Date: Sat, 3 May 2008 15:00:39 -0700 [thread overview]
Message-ID: <402c10cd0805031500m234dcc7bu72682e1b8b821d1e@mail.gmail.com> (raw)
In-Reply-To: <m3tzhqp96h.fsf@localhost.localdomain>
On Fri, Apr 25, 2008 at 2:37 AM, Jakub Narebski <jnareb@gmail.com> wrote:
>
> I think you should describe here _what_ is tested by the new test(s),
> and how it is named.
I do not intend to use more time on this. They follow more or less
the same outline as t7600.
--
Sverre Hvammen Johansen
prev parent reply other threads:[~2008-05-03 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 5:43 [PATCH 1/5] New merge tests Sverre Hvammen Johansen
2008-04-25 9:37 ` Jakub Narebski
2008-05-03 22:00 ` Sverre Hvammen Johansen [this message]
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=402c10cd0805031500m234dcc7bu72682e1b8b821d1e@mail.gmail.com \
--to=hvammen@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@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).