From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Pat Thoyts <patthoyts@gmail.com>
Cc: Peter Harris <pharris@opentext.com>,
Pat Thoyts <patthoyts@users.sourceforge.net>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, msysgit@googlegroups.com,
sschuberth@gmail.com
Subject: Re: [msysGit] Re: [PULL] Pull request from msysGit
Date: Sat, 09 Oct 2010 18:56:11 +0100 [thread overview]
Message-ID: <4CB0ACBB.9040601@ramsay1.demon.co.uk> (raw)
In-Reply-To: <AANLkTinSjFDdwqTEU6XzOVHupph0G2ZKM+u3r7t_W3DD@mail.gmail.com>
Pat Thoyts wrote:
> The patch in question has been on the msysGit tree for about 10 months
> now. Its somewhat disappointing not to have had it spotted before we
> pushed it upstream. Are the msvc builders only working against junio's
> repository?
Well, I can't speak for anyone else, but for me the answer is yes. ;-)
I build git (from the git.kernel.org repository) on Linux, cygwin,
cygwin+msvc and msysGit. (For a short while I also built it on FreeBSD
hosted in a VM - but that was so slow, I soon stopped doing that!).
So, the git I *use* on MinGW/msysGit is built from junio's repository.
I only installed msysGit to enable me to check that my patches worked
on MinGW (I was tired of always saying "could somebody test this on
MinGW ..."). As you may have noticed, the mingw and msvc builds share
quite a bit of compatibility code...
[I don't follow 4msysgit or subscribe to the msysgit mailing list, so
I would not normally see any 4msysgit patches, unless they were also
discussed on the git mailing list.]
ATB,
Ramsay Jones
prev parent reply other threads:[~2010-10-09 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 23:52 [PULL] Pull request from msysGit Pat Thoyts
2010-10-05 16:45 ` Junio C Hamano
2010-10-07 17:17 ` Ramsay Jones
2010-10-07 19:30 ` Peter Harris
2010-10-07 20:18 ` [msysGit] " Pat Thoyts
2010-10-07 20:22 ` Erik Faye-Lund
2010-10-09 17:56 ` Ramsay Jones [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
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=4CB0ACBB.9040601@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=msysgit@googlegroups.com \
--cc=patthoyts@gmail.com \
--cc=patthoyts@users.sourceforge.net \
--cc=pharris@opentext.com \
--cc=sschuberth@gmail.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).