From: Sverre Rabbelier <srabbelier@gmail.com>
To: Lahiru Perera <lahiru@providencesl.com>
Cc: git@vger.kernel.org
Subject: Re: Problem in pushing git
Date: Mon, 2 Mar 2009 08:51:44 +0100 [thread overview]
Message-ID: <fabb9a1e0903012351r9e881f7w64601ec1b1fad9e6@mail.gmail.com> (raw)
In-Reply-To: <49AB8B4F.90006@providencesl.com>
Heya,
On Mon, Mar 2, 2009 at 08:31, Lahiru Perera <lahiru@providencesl.com> wrote:
> Im finding a solution from last few month
I'm glad to hear that you've been trying to find the solution
yourself, but why did you not look at the faq [0]? The exact same
question you asked has been answered there (see [0]).
[0] http://git.or.cz/gitwiki/GitFaq#head-b96f48bc9c925074be9f95c0fce69bcece5f6e73
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-03-02 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 7:31 Problem in pushing git Lahiru Perera
2009-03-02 7:51 ` Sverre Rabbelier [this message]
2010-08-16 15:55 ` Bruno Furtado
2010-08-16 16:30 ` Junio C Hamano
2010-08-16 17:52 ` Bruno Furtado
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=fabb9a1e0903012351r9e881f7w64601ec1b1fad9e6@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=lahiru@providencesl.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).