git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Benoit Bourbie <benoit.bourbie@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Fixing typos
Date: Thu, 11 Apr 2013 15:44:49 +0530	[thread overview]
Message-ID: <CALkWK0kwm-sFevWhZ1XwZGzozbJ_VwGkSt16FJtb67q10sqS+A@mail.gmail.com> (raw)
In-Reply-To: <5166291C.8070709@gmail.com>

Benoit Bourbie wrote:
> I apologize for being picky

There's nothing to apologize for.  These are good catches worth fixing.

> but that patch fixes 3 typos.

Please read Documentation/SubmittingPatches, particularly the parts about:
1. Sending patches inline using git send-email, as opposed to an attachment.
2. Signing off on your patch.

Cheers.

  reply	other threads:[~2013-04-11 10:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11  3:08 Fixing typos Benoit Bourbie
2013-04-11 10:14 ` Ramkumar Ramachandra [this message]
2013-04-12  5:20   ` Benoit Bourbie

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=CALkWK0kwm-sFevWhZ1XwZGzozbJ_VwGkSt16FJtb67q10sqS+A@mail.gmail.com \
    --to=artagnon@gmail.com \
    --cc=benoit.bourbie@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).