From: "Carlos Martín Nieto" <carlos@cmartin.tk>
To: Dmitry Ivankov <divanorama@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix typo: existant->existent
Date: Thu, 16 Jun 2011 15:19:40 +0200 [thread overview]
Message-ID: <20110616131938.GA7751@centaur.lab.cmartin.tk> (raw)
In-Reply-To: <1308223595-6319-1-git-send-email-divanorama@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
On Thu, Jun 16, 2011 at 05:26:35PM +0600, Dmitry Ivankov wrote:
> refs.c had a error message "Trying to write ref with nonexistent object".
From the patch, ITYM to say "with nonexistant object" here
Cheers,
cmn
--
Carlos Martín Nieto | http://cmartin.tk
"¿Cómo voy a decir bobadas si soy mudo?" -- CACHAI
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-06-16 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 11:26 [PATCH] Fix typo: existant->existent Dmitry Ivankov
2011-06-16 13:19 ` Carlos Martín Nieto [this message]
2011-06-16 13:28 ` Dmitry Ivankov
2011-06-16 13:42 ` Dmitry Ivankov
-- strict thread matches above, loose matches on Subject: below --
2011-06-16 12:22 Dmitry Ivankov
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=20110616131938.GA7751@centaur.lab.cmartin.tk \
--to=carlos@cmartin.tk \
--cc=divanorama@gmail.com \
--cc=git@vger.kernel.org \
/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).