From: Sverre Rabbelier <srabbelier@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: "What's cooking" incremental edition
Date: Sun, 10 Jan 2010 15:21:20 -0500 [thread overview]
Message-ID: <fabb9a1e1001101221i389c05a8v7ff241859d5e8dae@mail.gmail.com> (raw)
In-Reply-To: <7vmy0lpwes.fsf@alter.siamese.dyndns.org>
Heya,
On Sun, Jan 10, 2010 at 14:55, Junio C Hamano <gitster@pobox.com> wrote:
> * jn/makefile (2010-01-06) 4 commits
> - - Makefile: consolidate .FORCE-* targets
> - - Makefile: learn to generate listings for targets requiring special flags
> - - Makefile: use target-specific variable to pass flags to cc
> - - Makefile: regenerate assembler listings when asked
> + (merged to 'next' on 2010-01-10 at f5a5d42)
> + + Makefile: consolidate .FORCE-* targets
> + + Makefile: learn to generate listings for targets requiring special flags
> + + Makefile: use target-specific variable to pass flags to cc
> + + Makefile: regenerate assembler listings when asked
Fwiw, I find it harder to read due to the now ambiguous meaning of the
+ and - (it could either mean something is in pu/next, or that the
topic changed). Of course this is partly caused by the fact that I
don't read emails in fixed font (by default), but perhaps it's worth
considering using different symbols for pu/next-ness?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-01-10 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 19:55 "What's cooking" incremental edition Junio C Hamano
2010-01-10 20:21 ` Sverre Rabbelier [this message]
2010-01-12 16:27 ` Jeff King
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=fabb9a1e1001101221i389c05a8v7ff241859d5e8dae@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).