From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Bradford Smith <bradford.carl.smith@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [Bradford C. Smith] [PATCH 2/2] use lockfile.c routines in git_commit_set_multivar()
Date: Thu, 26 Jul 2007 19:26:51 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707261926340.14781@racer.site> (raw)
In-Reply-To: <f158199e0707261040u70ee31d3le2eaf21ab1302909@mail.gmail.com>
Hi,
On Thu, 26 Jul 2007, Bradford Smith wrote:
> Dear Dscho,
>
> I've submitted a slightly modified version of the same patch to the list.
> It fixes a comment format to match the approved style for git code. Please
> review that one instead.
I saw it and am reviewing it!
Ciao,
Dscho
prev parent reply other threads:[~2007-07-26 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 23:39 [Bradford C. Smith] [PATCH 2/2] use lockfile.c routines in git_commit_set_multivar() Junio C Hamano
2007-07-26 3:31 ` Johannes Schindelin
[not found] ` <f158199e0707261040u70ee31d3le2eaf21ab1302909@mail.gmail.com>
2007-07-26 18:26 ` Johannes Schindelin [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=Pine.LNX.4.64.0707261926340.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=bradford.carl.smith@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).