git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jens Lehmann <Jens.Lehmann@web.de>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jul 2013, #07; Sun, 21)
Date: Mon, 22 Jul 2013 22:47:38 +0200	[thread overview]
Message-ID: <51ED9A6A.8050502@web.de> (raw)
In-Reply-To: <CACsJy8BsiXL9P5Rd9QZzG5Rtyd=0ewBbFRLwbAyumgTWwjJd5A@mail.gmail.com>

Am 22.07.2013 09:48, schrieb Duy Nguyen:
> On Mon, Jul 22, 2013 at 2:32 PM, Jens Lehmann <Jens.Lehmann@web.de> wrote:
>> Am 22.07.2013 08:57, schrieb Junio C Hamano:
>>> * jl/submodule-mv (2013-04-23) 5 commits
>>>  . submodule.c: duplicate real_path's return value
>>>  . rm: delete .gitmodules entry of submodules removed from the work tree
>>>  . Teach mv to update the path entry in .gitmodules for moved submodules
>>>  . Teach mv to move submodules using a gitfile
>>>  . Teach mv to move submodules together with their work trees
>>>
>>>  "git mv A B" when moving a submodule A does "the right thing",
>>>  inclusing relocating its working tree and adjusting the paths in
>>>  the .gitmodules file.
>>>
>>>  Ejected from 'pu', as it conflicts with nd/magic-pathspec.
>>
>> So I'll base my upcoming re-roll on pu, right?
> 
> The conflicted part is the use of common_prefix. I think you might be
> able to avoid the conflict by using quote.c:path_relative() instead of
> common_prefix() and prepending "../" manually. Or not, I did not read
> path_relative() carefully, nor your connect_work_tree_and_git_dir().

Thanks for the pointers, I'll look into that.

  reply	other threads:[~2013-07-22 20:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22  6:57 What's cooking in git.git (Jul 2013, #07; Sun, 21) Junio C Hamano
2013-07-22  7:15 ` Eric Sunshine
2013-07-22  7:32 ` Jens Lehmann
2013-07-22  7:48   ` Duy Nguyen
2013-07-22 20:47     ` Jens Lehmann [this message]
2013-07-28 17:23       ` Jens Lehmann
2013-07-22 10:39 ` Thomas Rast
2013-07-22 21:39 ` Yamada Saburo
2013-07-22 22:12   ` Junio C Hamano
2013-07-22 22:22 ` John Keeping
2013-07-22 23:13 ` Torsten Bögershausen
2013-07-24 19:03   ` Ramsay Jones

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=51ED9A6A.8050502@web.de \
    --to=jens.lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@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.
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).