From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Subject: Re: What's cooking in git.git (Nov 2009, #01; Wed, 04)
Date: Thu, 05 Nov 2009 09:38:55 +0100 [thread overview]
Message-ID: <4AF28F1F.7020905@viscovery.net> (raw)
In-Reply-To: <7vmy31a5p6.fsf@alter.siamese.dyndns.org>
Junio C Hamano schrieb:
> * rj/maint-simplify-cygwin-makefile (2009-10-27) 1 commit.
> - Makefile: merge two Cygwin configuration sections into one
>
> This is one of the most obviously correct bit from "Compiling on Cygwin
> using MSVC fails" topic I didn't really look at. If J6t is Ok with the
> series, I don't mind queueing the whole thing myself.
I'm actually expecting a resend of the remaining patches in the series
with updated commit messages and with the original patch 3/4 being first.
-- Hannes
prev parent reply other threads:[~2009-11-05 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 5:41 What's cooking in git.git (Nov 2009, #01; Wed, 04) Junio C Hamano
2009-11-05 8:38 ` Johannes Sixt [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=4AF28F1F.7020905@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ramsay@ramsay1.demon.co.uk \
/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).