From: dhruva <dhruvakm@gmail.com>
To: "Johannes Sixt" <j.sixt@viscovery.net>
Cc: Git <git@vger.kernel.org>, msysGit <msysgit@googlegroups.com>
Subject: Re: [msysGit] Re: git build on msys fails (and fix)
Date: Mon, 1 Dec 2008 19:00:55 +0530 [thread overview]
Message-ID: <e3f230850812010530h49fc360eu309876a4ebbb0f9d@mail.gmail.com> (raw)
In-Reply-To: <e3f230850812010507y54dff6dh3757bf97c78c0329@mail.gmail.com>
Hi,
Sorry for all the noise, I pushed the files. I had to use:
$ git push mob@repo.or.cz:/srv/git/msysgit.git
-dhruva
--
Contents reflect my personal views only!
prev parent reply other threads:[~2008-12-01 13:32 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
2008-12-01 13:07 ` dhruva
2008-12-01 13:30 ` dhruva [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e3f230850812010530h49fc360eu309876a4ebbb0f9d@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).