From: "David Symonds" <dsymonds@gmail.com>
To: "Martin Koegler" <mkoegler@auto.tuwien.ac.at>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Document conding style
Date: Wed, 27 Feb 2008 19:36:28 +1100 [thread overview]
Message-ID: <ee77f5c20802270036o7e792feqd110b7ea96a3b75c@mail.gmail.com> (raw)
In-Reply-To: <12041000101604-git-send-email-mkoegler@auto.tuwien.ac.at>
On Wed, Feb 27, 2008 at 7:13 PM, Martin Koegler
<mkoegler@auto.tuwien.ac.at> wrote:
> + - Consider checking your patches with checkpatch from the linux
> + kernel. It helps you to spot trivial formating errors.
> +
Consider checking your spelling, too? ;-)
Dave.
next prev parent reply other threads:[~2008-02-27 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 8:13 [PATCH] Document conding style Martin Koegler
2008-02-27 8:36 ` David Symonds [this message]
2008-02-27 9:43 ` Johannes Schindelin
2008-02-28 13:07 ` Jean-Luc Herren
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ee77f5c20802270036o7e792feqd110b7ea96a3b75c@mail.gmail.com \
--to=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mkoegler@auto.tuwien.ac.at \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).