git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Junio Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 3/3] rev-list --bisect: Bisection "distance" clean up.
Date: Sat, 15 Sep 2007 12:15:52 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709151215090.28586@racer.site> (raw)
In-Reply-To: <20070915130016.eac885f4.chriscool@tuxfamily.org>

Hi Christian,

you did not provide any meaningful commit message.  I feel that this would 
be needed in this case, _especially_ since there was no cover letter to 
describe what the heck this patch series fixes.

Ciao,
Dscho

  reply	other threads:[~2007-09-15 11:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-15 11:00 [PATCH 3/3] rev-list --bisect: Bisection "distance" clean up Christian Couder
2007-09-15 11:15 ` Johannes Schindelin [this message]
2007-09-15 11:47   ` Christian Couder
2007-09-16  8:54 ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2007-09-17  3:28 Christian Couder

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=Pine.LNX.4.64.0709151215090.28586@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).