git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Alexey Pelykh <alexey.pelykh@gmail.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Junio C Hamano <gitster@pobox.com>,
	"Matt Seitz (matseitz)" <matseitz@cisco.com>,
	git@vger.kernel.org
Subject: Re: Question about submodules and absolute paths
Date: Wed, 23 May 2012 10:32:38 +0300	[thread overview]
Message-ID: <CAOmKuSqUm+WoTA5U5ZSgqFS6Oc7q+y8wSR0sMxHW_EPKoz6fwQ@mail.gmail.com> (raw)
In-Reply-To: <4FBC90C2.6050203@web.de>

Great! I'll try git from sources then

On Wed, May 23, 2012 at 10:24 AM, Jens Lehmann <Jens.Lehmann@web.de> wrote:
>
> Am 22.05.2012 23:06, schrieb Junio C Hamano:
> > Didn't the submodule folks worked on the related area recently, and
> > doesn't the result of their work already in v1.7.10?
> >
> > I am thinking specifically about the series around d75219b (submodules:
> > always use a relative path from gitdir to work tree, 2012-03-04).  Jens?
>
> Yes, these changes should fix the problem described by Alexey.

  reply	other threads:[~2012-05-23  7:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOmKuSoYP9fYORDy5twLpFh7SQ7rc6x2A=F8XjfKMqo-ErCauQ@mail.gmail.com>
2012-05-22 11:36 ` Question about submodules and absolute paths Alexey Pelykh
2012-05-22 18:27   ` Junio C Hamano
2012-05-22 19:18     ` Alexey Pelykh
2012-05-22 19:25       ` Matt Seitz (matseitz)
2012-05-22 19:29         ` Alexey Pelykh
2012-05-22 19:36           ` Matt Seitz (matseitz)
2012-05-22 20:25             ` Alexey Pelykh
2012-05-22 21:06               ` Junio C Hamano
2012-05-23  7:24                 ` Jens Lehmann
2012-05-23  7:32                   ` Alexey Pelykh [this message]
2012-05-23 20:42                     ` Jens Lehmann
2012-05-24  5:08                       ` Alexey Pelykh
2012-05-23  5:36       ` Johannes Sixt
2012-05-23  5:39         ` Alexey Pelykh

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOmKuSqUm+WoTA5U5ZSgqFS6Oc7q+y8wSR0sMxHW_EPKoz6fwQ@mail.gmail.com \
    --to=alexey.pelykh@gmail.com \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=matseitz@cisco.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).