From: Marius Storm-Olsen <marius@trolltech.com>
To: Johannes Sixt <j.sixt@telecom.at>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] Introduces xmkstemp()
Date: Fri, 31 Aug 2007 11:00:20 +0200 [thread overview]
Message-ID: <46D7D8A4.1060800@trolltech.com> (raw)
In-Reply-To: <46D7D60C.8090608@telecom.at>
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
Johannes Sixt said the following on 31.08.2007 10:49:
> Marius Storm-Olsen schrieb:
>> Just wanted to let the original author know, so he would be aware
>> of it, and we wouldn't have to go the extra round-trips with
>> patches to fix patches. (And for MinGW awareness when adding code
>> to git-compat-util.h)
>
> You can't expect a lot of MinGW awareness from non-MinGW users when
> they make changes to git-compat-util.h since upstream does not have
> _any_ references to MinGW there, yet.
D'oh!
/me smacks self
We really need to streamline the patches needed for MinGW, and get
those merged into upstream when 1.5.3 is released.
--
.marius
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2007-08-31 9:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 19:44 [PATCH 1/2] Introduces xmkstemp() Luiz Fernando N. Capitulino
2007-08-15 15:11 ` Carlos Rica
2007-08-15 16:17 ` Luiz Fernando N. Capitulino
2007-08-15 16:47 ` Carlos Rica
2007-08-31 8:27 ` Marius Storm-Olsen
2007-08-31 8:34 ` Johannes Sixt
2007-08-31 8:42 ` Marius Storm-Olsen
2007-08-31 8:49 ` Johannes Sixt
2007-08-31 9:00 ` Marius Storm-Olsen [this message]
2007-08-31 12:03 ` MinGW merge plans, was " Johannes Schindelin
2007-08-31 13:13 ` Johannes Sixt
2007-08-31 16:57 ` Luiz Fernando N. Capitulino
2007-08-31 12:48 ` Luiz Fernando N. Capitulino
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=46D7D8A4.1060800@trolltech.com \
--to=marius@trolltech.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@telecom.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.