git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alon Ziv <alonz@nolaviz.org>
To: git@vger.kernel.org
Subject: MinGW port: some questions
Date: Wed, 16 May 2007 21:52:00 +0300	[thread overview]
Message-ID: <1179341520.31213.38.camel@bruno.nolaviz.org> (raw)

Hi,

I am looking at the MinGW port, and I see some rather strange changes
included in the port; "strange" in the sense that they do not appear to
have anything to do with MinGW.

I am referring, for example, to the changes from commit dc380d6, which
were reverted in Git mainline (actually in "next", they never reached
Git's "master").  Or to the changes from 4493e36, which had the same
fate.

Are these intentional?  Or are they the result of some strange mismerge?

	-az

             reply	other threads:[~2007-05-16 18:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 18:52 Alon Ziv [this message]
2007-05-16 19:09 ` MinGW port: some questions Junio C Hamano
2007-05-16 19:55   ` Alon Ziv
2007-05-18  7:58   ` 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=1179341520.31213.38.camel@bruno.nolaviz.org \
    --to=alonz@nolaviz.org \
    --cc=git@vger.kernel.org \
    /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).