From: Tim Olsen <tim@brooklynpenguin.com>
To: unlisted-recipients:; (no To-header on input)
Cc: git@vger.kernel.org
Subject: Re: still getting 'It is a submodule!" in 1.6.2.5
Date: Tue, 05 May 2009 11:23:50 -0400 [thread overview]
Message-ID: <4A005A06.6040209@brooklynpenguin.com> (raw)
In-Reply-To: <4A004BCA.5070709@brooklynpenguin.com>
Tim Olsen wrote:
> Thanks Junio for your reply. We have made a copy of the offending
> branch by hand and have managed to merge that instead for now. I can
> wait until 1.6.3 is released.
I changed my mind and decided to try out 1.6.3.rc4. I can confirm that
the bug is fixed. Thanks!
Tim
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
next prev parent reply other threads:[~2009-05-05 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 20:39 still getting 'It is a submodule!" in 1.6.2.5 Tim Olsen
2009-05-05 6:43 ` Junio C Hamano
2009-05-05 14:23 ` Tim Olsen
2009-05-05 15:23 ` Tim Olsen [this message]
2009-05-06 7:31 ` Matthias Andree
[not found] ` <20090506180925.6117@nanako3.lavabit.com>
2009-05-06 9:57 ` Matthias Andree
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=4A005A06.6040209@brooklynpenguin.com \
--to=tim@brooklynpenguin.com \
--cc=git@vger.kernel.org \
/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).