All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <johannes.sixt@telecom.at>
Cc: msysGit <msysgit@googlegroups.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [msysGit] Re: MinGW port pull request
Date: Sat, 21 Jun 2008 14:47:05 -0700	[thread overview]
Message-ID: <7vve028nqe.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <200806212318.47745.johannes.sixt@telecom.at> (Johannes Sixt's message of "Sat, 21 Jun 2008 23:18:47 +0200")

Johannes Sixt <johannes.sixt@telecom.at> writes:

> * The #ifdef in setup.c, prefix_filename() could easily be removed by using 
> the MINGW32 arm everywhere. This would penalize non-Windows, however, 
> prefix_filename() is not performance critical.
>
>>  * There is an interaction with dr/ceiling topic that is already in 'next'
>>    that needs to be resolved before we merge this in 'next'.
>
> How do you want me to proceed? Rebase on top of dr/ceiling? Wait until 
> dr/ceiling is in master and rebase again? Merge it into my series? (I would 
> make the merge the last commit in my series.) I'm asking because support of 
> dr/ceiling was not overwhelming.

I personally feel MinGW branch is more important than ceiling work, not
just because it targets far wider audience but because it affects a lot
wider area.  j6t/mingw _will_ eventually graduate to master in some form
(possibly after fixups that is needed to keep things working on non
Windows environment), and dr/ceil may or may not.

So my preference would be to merge j6t/mingw into dr/ceil branch soon,
resolve conflicts there, and merge the result to 'next' when j6t/mingw is
merged to 'next' at the same time.  And you can help with that merge when
it happens.

  parent reply	other threads:[~2008-06-21 21:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20  8:06 MinGW port pull request Johannes Sixt
2008-06-21  9:46 ` Junio C Hamano
2008-06-21 21:18   ` [msysGit] " Johannes Sixt
2008-06-21 21:21     ` Jim Raden
2008-06-21 21:47     ` Junio C Hamano [this message]
2008-06-23 11:54     ` Johannes Sixt
2008-06-24 13:01   ` Johannes Sixt

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=7vve028nqe.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.sixt@telecom.at \
    --cc=msysgit@googlegroups.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 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.