Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Chris Frey <cdfrey@foursquare.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Updating documentation to match Brandon Casey's proposed git-repack patch.
Date: Wed, 14 May 2008 09:26:26 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.1.00.0805140925060.30431@racer> (raw)
In-Reply-To: <20080514072514.GA26202@foursquare.net>

Hi,

On Wed, 14 May 2008, Chris Frey wrote:

> I haven't heard any negative commentary on this patch, and I see
> the repack patch is in next, so resending in case it was missed.

This part, together with the subject, is not really meant for application 
as-is, is it?  Please follow the guidelines for SubmittingPatches, and 
write supporting arguments that are not meant to be part of the commit 
messages _after_ the "---".

Ciao,
Dscho

  reply	other threads:[~2008-05-14  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14  7:25 [PATCH] Updating documentation to match Brandon Casey's proposed git-repack patch Chris Frey
2008-05-14  8:26 ` Johannes Schindelin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-08 21:40 git gc & deleted branches Brandon Casey
2008-05-08 21:44 ` Jeff King
2008-05-08 21:53   ` Brandon Casey
2008-05-08 22:48     ` Jeff King
2008-05-09  1:41       ` Brandon Casey
2008-05-09  4:19         ` Jeff King
2008-05-09 15:00           ` Geert Bosch
2008-05-09 15:14             ` Brandon Casey
2008-05-09 16:12               ` Nicolas Pitre
2008-05-09 22:33                 ` Junio C Hamano
2008-05-09 23:09                   ` [PATCH] Updating documentation to match Brandon Casey's proposed git-repack patch Chris Frey

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=alpine.DEB.1.00.0805140925060.30431@racer \
    --to=johannes.schindelin@gmx.de \
    --cc=cdfrey@foursquare.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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