git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>, Duy Nguyen <pclouds@gmail.com>,
	Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [RFC/PATCH] clone: introduce clone.submoduleGitDir to relocate $GITDIR
Date: Wed, 17 Apr 2013 08:48:07 -0700	[thread overview]
Message-ID: <20130417154807.GA3499@elie.Belkin> (raw)
In-Reply-To: <CALkWK0kDgSicNejydLsH6iqj-yDYGz6CKd+kbn4EW1HxgAxsBA@mail.gmail.com>

Ramkumar Ramachandra wrote:

> 2. This ugliness complicates implementation of add/ rm/ mv, because
> each of them will have to know about this contrived path solution.

Why is that?  Can't they look at the gitfile or call some helper
(that happens to be part of the same binary)?

  parent reply	other threads:[~2013-04-17 15:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13 19:23 [RFC/PATCH] clone: introduce clone.submoduleGitDir to relocate $GITDIR Ramkumar Ramachandra
2013-04-15  1:28 ` Junio C Hamano
2013-04-15  2:48   ` Junio C Hamano
2013-04-15  8:08     ` Ramkumar Ramachandra
2013-04-15 10:14       ` Junio C Hamano
2013-04-15 11:35         ` Ramkumar Ramachandra
2013-04-15  7:59   ` Ramkumar Ramachandra
2013-04-15  8:19   ` Ramkumar Ramachandra
2013-04-15  9:25     ` Duy Nguyen
2013-04-15  9:47       ` Ramkumar Ramachandra
2013-04-15  9:45     ` Junio C Hamano
2013-04-15 11:48       ` Ramkumar Ramachandra
2013-04-15 15:50     ` Marc Branchaud
2013-04-15 17:50       ` Junio C Hamano
2013-04-15 18:00         ` Ramkumar Ramachandra
2013-04-15 18:43           ` Jeff King
2013-04-15 20:52             ` Junio C Hamano
2013-04-16  8:13             ` Ramkumar Ramachandra
2013-04-16 15:39               ` Marc Branchaud
2013-04-15 18:50           ` Marc Branchaud
2013-04-16  8:17             ` Ramkumar Ramachandra
2013-04-16 15:46               ` Marc Branchaud
2013-04-15 18:43         ` Marc Branchaud
2013-04-15 18:50           ` Junio C Hamano
2013-04-15 20:32             ` Marc Branchaud
2013-04-15 20:56               ` Junio C Hamano
2013-04-16  8:21             ` Ramkumar Ramachandra
2013-04-16 15:46               ` Marc Branchaud
2013-04-15 17:50       ` Ramkumar Ramachandra
2013-04-16  2:58 ` Jonathan Nieder
2013-04-16  8:36   ` Ramkumar Ramachandra
2013-04-16 17:28     ` Junio C Hamano
2013-04-17 15:48     ` Jonathan Nieder [this message]
2013-04-17 10:22 ` Duy Nguyen
2013-04-17 10:53   ` Ramkumar Ramachandra
2013-04-17 10:59     ` Duy Nguyen
2013-04-17 11:13       ` Ramkumar Ramachandra
2013-04-17 11:36         ` Duy Nguyen
2013-04-17 15:02           ` Ramkumar Ramachandra
2013-04-17 23:01             ` Duy Nguyen
2013-04-17 17:18           ` Junio C Hamano

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=20130417154807.GA3499@elie.Belkin \
    --to=jrnieder@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@gmail.com \
    --cc=peff@peff.net \
    /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).