git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Robert Schiele <rschiele@gmail.com>,
	Zoltan Klinger <zoltan.klinger@gmail.com>,
	GIT Mailing-list <git@vger.kernel.org>
Subject: Re: Unused #include statements
Date: Thu, 15 Jan 2015 19:00:36 -0500	[thread overview]
Message-ID: <20150116000035.GC25120@peff.net> (raw)
In-Reply-To: <xmqqy4p34onq.fsf@gitster.dls.corp.google.com>

On Thu, Jan 15, 2015 at 03:20:09PM -0800, Junio C Hamano wrote:

> OK, thanks.  Let's queue something like this for post 2.3 cycle,
> then.
> 
> -- >8 --
> Subject: CodingGuidelines: clarify C #include rules
> [...]

Thanks, this looks good to me.

-Peff

  reply	other threads:[~2015-01-16  0:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15  3:43 Unused #include statements Zoltan Klinger
2015-01-15  4:14 ` Robert Schiele
2015-01-15  6:33   ` Jeff King
2015-01-15 18:50     ` Junio C Hamano
2015-01-15 22:38       ` Jeff King
2015-01-15 23:20         ` Junio C Hamano
2015-01-16  0:00           ` Jeff King [this message]
2015-01-20  2:08       ` Zoltan Klinger

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=20150116000035.GC25120@peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=rschiele@gmail.com \
    --cc=zoltan.klinger@gmail.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).