From: Jon Seymour <jon.seymour@gmail.com>
To: Eric Blake <eblake@redhat.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Ramsay Allan Jones <ramsay@ramsay1.demon.co.uk>,
Dmitry Potapov <dpotapov@gmail.com>
Subject: Re: Are the patches used to build git on cygwin available in a git repo somewhere?
Date: Wed, 31 Mar 2010 23:58:18 +1200 [thread overview]
Message-ID: <w2y2cfc40321003310458vc0fc3dddjb47a8a7dddb1c41e@mail.gmail.com> (raw)
In-Reply-To: <4BB336C1.4000504@redhat.com>
On Wed, Mar 31, 2010 at 11:49 PM, Eric Blake <eblake@redhat.com> wrote:
> According to Jon Seymour on 3/31/2010 1:55 AM:
>> What I was looking for was a git repo that contains a branch with the
>> patches that the cygwin folks mutate the official git release with.
>> Such a repo would be quite useful because people could, in theory, use
>> these to produce their own cygwin git builds at arbitrary commits
>> instead of having to wait for cygwin to catch up.
>>
>> Admittedly, it is not a big deal to build such a branch using the
>> patch from the cygwin package source, but I was just wondering whether
>> there was a well-known repo that contained the patches already.
>
> Nope - the patchset that I apply when building the cygwin port is so small
> that so far I have just maintained it manually, rather than publishing a
> git repo. But if you want me to make it more public, I can certainly look
> into doing that. And yes, now that 1.7.x is out for some time now, I
> should probably advance the cygwin port beyond 1.6.6.1.
>
As you say, it's probably not worth the effort, but if you ever do
decide to set such a thing up, do let me know.
jon.
> --
> Eric Blake eblake@redhat.com +1-801-349-2682
> Libvirt virtualization library http://libvirt.org
>
>
next prev parent reply other threads:[~2010-03-31 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 16:16 Are the patches used to build git on cygwin available in a git repo somewhere? Jon Seymour
2010-03-31 2:56 ` Jonathan Nieder
2010-03-31 2:58 ` Jonathan Nieder
2010-03-31 7:55 ` Jon Seymour
2010-03-31 11:49 ` Eric Blake
2010-03-31 11:58 ` Jon Seymour [this message]
2010-04-01 2:35 ` Jonathan Nieder
2010-04-01 20:59 ` Eric Blake
2010-04-01 23:41 ` Jon Seymour
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=w2y2cfc40321003310458vc0fc3dddjb47a8a7dddb1c41e@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=dpotapov@gmail.com \
--cc=eblake@redhat.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.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).