From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Cc: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 3/5] pretty describe: move library functions to the new file describe.c
Date: Sun, 4 Nov 2007 14:36:44 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711041435540.4362@racer.site> (raw)
In-Reply-To: <472DB199.2040305@lsrfire.ath.cx>
Hi,
On Sun, 4 Nov 2007, Ren? Scharfe wrote:
> Makefile | 2 +-
> builtin-describe.c | 202 ---------------------------------------------------
> cache.h | 5 ++
> describe.c | 204 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 210 insertions(+), 203 deletions(-)
> create mode 100644 describe.c
Would not "format-patch -C -C" have given a nicer output?
Ciao,
Dscho
next prev parent reply other threads:[~2007-11-04 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 11:48 [PATCH 3/5] pretty describe: move library functions to the new file describe.c René Scharfe
2007-11-04 14:36 ` Johannes Schindelin [this message]
2007-11-04 14:56 ` René Scharfe
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.0711041435540.4362@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=rene.scharfe@lsrfire.ath.cx \
/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).