public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: David Aguilar <davvid@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Sep 2014, #09; Tue, 30)
Date: Thu, 02 Oct 2014 10:46:55 -0700	[thread overview]
Message-ID: <xmqqvbo2nz3k.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20141001040124.GA32748@gmail.com> (David Aguilar's message of "Tue, 30 Sep 2014 21:01:25 -0700")

David Aguilar <davvid@gmail•com> writes:

> On Tue, Sep 30, 2014 at 01:23:18PM -0700, Junio C Hamano wrote:
>> Here are the topics that have been cooking.  Commits prefixed with
>> '-' are only in 'pu' (proposed updates) while commits prefixed with
>> '+' are in 'next'.
>> 
>> * da/include-compat-util-first-in-c (2014-09-15) 4 commits
>>  - SQUASH???
>>  - check-headers: add header usage checks for .c files
>>  - Makefile: add check-headers target
>>  - cleanups: ensure that git-compat-util.h is included first
>> 
>>  So... what is happening to this topic?  I think the bottom one is a
>>  reasonable clean-up without too much churn, but I am not sure about
>>  the rest.
>
> Agreed. The SQUASH??? commit could be squashed in, but it might
> just be better to take the bottom commit and drop the rest since
> they aren't really that helpful.

OK, let's do that.

      reply	other threads:[~2014-10-02 17:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 20:23 What's cooking in git.git (Sep 2014, #09; Tue, 30) Junio C Hamano
2014-09-30 20:47 ` W. Trevor King
2014-09-30 21:09   ` Junio C Hamano
2014-10-01  4:01 ` David Aguilar
2014-10-02 17:46   ` Junio C Hamano [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=xmqqvbo2nz3k.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=davvid@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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