From: dhruva <dhruvakm@gmail.com>
To: "Johannes Sixt" <j.sixt@viscovery.net>
Cc: Git <git@vger.kernel.org>, msysGit <msysgit@googlegroups.com>
Subject: Re: git build on msys fails (and fix)
Date: Mon, 1 Dec 2008 17:32:20 +0530 [thread overview]
Message-ID: <e3f230850812010402n69cced19s3f36a5bcb84977c6@mail.gmail.com> (raw)
In-Reply-To: <4933D10E.6020706@viscovery.net>
Hello,
On Mon, Dec 1, 2008 at 5:27 PM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> dhruva schrieb:
>> I got the mob branch and I fail to see the Makefile. I decided to
>> just add the pthread related files and push so that someone could
>> build, I get authentication failures. I had tried to push perl
>> sometime back when I had a gcc compiler perl (before strawberry perl)
>> and had similar problems. I am fairly certain I am doing something
>> wrong but cannot figure it out!
>
> msysgit.git is *not* a git.git clone; it is the MSYS/MinGW environment to
> build git.git on Windows.
>
> You should apply the steps 1. to 4. that you mentioned in an earlier mail
> and push the result; but you cannot apply 5. because that is a change to
> git itself.
I request someone to just pull the archive I have placed just this
time, I will try again for other patches. I will create a clone in a
separate folder for msysgit and keep it ready. Unknowingly, I just
cleaned up the remote and lost all the changes I had pulled earlier :(
-dhruva
--
Contents reflect my personal views only!
next prev parent reply other threads:[~2008-12-01 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-30 11:02 git build on msys fails (and fix) dhruva
2008-11-30 11:52 ` dhruva
2008-12-01 9:06 ` Johannes Sixt
2008-12-01 9:32 ` dhruva
2008-12-01 10:52 ` dhruva
2008-12-01 11:48 ` dhruva
2008-12-01 11:57 ` Johannes Sixt
2008-12-01 12:02 ` dhruva [this message]
2008-12-01 13:07 ` dhruva
2008-12-01 13:30 ` [msysGit] " dhruva
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=e3f230850812010402n69cced19s3f36a5bcb84977c6@mail.gmail.com \
--to=dhruvakm@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--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 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).