From: Johannes Sixt <j6t@kdbg.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
Git Mailing List <git@vger.kernel.org>,
Antony Male <antony.male@gmail.com>,
Phil Hord <phil.hord@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
msysGit Mailinglist <msysgit@googlegroups.com>
Subject: Re: [PATCH v3 0/4] submodules: Use relative paths to gitdir and work tree
Date: Wed, 07 Mar 2012 21:40:46 +0100 [thread overview]
Message-ID: <4F57C7CE.1050005@kdbg.org> (raw)
In-Reply-To: <7v8vjcq5v3.fsf@alter.siamese.dyndns.org>
Am 07.03.2012 07:31, schrieb Junio C Hamano:
> Jens Lehmann <Jens.Lehmann@web.de> writes:
>> This is the third round of the former two patch series. It applies
>> cleanly on current master and maint and IMO is maint stuff as it fixes
>> bugs related to submodules. Those were introduced when moving the git
>> directory into that of the superproject and using a gitfile instead.
>
> I looked at this again and think this addresses the review comments
> made during the previous round, but I would like to get "Yay" from
> people who helped reviewing the previous round.
Yay. The topic passes the test suite.
-- Hannes
prev parent reply other threads:[~2012-03-07 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 21:11 [PATCH v3 0/4] submodules: Use relative paths to gitdir and work tree Jens Lehmann
2012-03-04 21:14 ` [PATCH v3 1/4] submodules: always use a relative path to gitdir Jens Lehmann
2012-03-04 21:15 ` [PATCH v3 2/4] submodules: always use a relative path from gitdir to work tree Jens Lehmann
2012-03-04 21:15 ` [PATCH v3 3/4] submodules: refactor computation of relative gitdir path Jens Lehmann
2012-03-04 21:16 ` [PATCH v3 4/4] submodules: fix ambiguous absolute paths under Windows Jens Lehmann
2012-03-07 6:31 ` [PATCH v3 0/4] submodules: Use relative paths to gitdir and work tree Junio C Hamano
2012-03-07 20:40 ` Johannes Sixt [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=4F57C7CE.1050005@kdbg.org \
--to=j6t@kdbg.org \
--cc=Jens.Lehmann@web.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=antony.male@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=msysgit@googlegroups.com \
--cc=phil.hord@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.