From: Antoine Tenart <antoine.tenart@ack.tf>
To: Junio C Hamano <gitster@pobox.com>
Cc: Antoine Tenart <antoine.tenart@ack.tf>,
git@vger.kernel.org, pclouds@gmail.com, sunshine@sunshineco.com
Subject: Re: [PATCH] worktree: add: introduce the --name option
Date: Tue, 19 Jul 2016 21:33:51 +0200 [thread overview]
Message-ID: <20160719193351.GC28551@kwain> (raw)
In-Reply-To: <xmqqh9blfntw.fsf@gitster.mtv.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
On Tue, Jul 19, 2016 at 12:08:11PM -0700, Junio C Hamano wrote:
> Antoine Tenart <antoine.tenart@ack.tf> writes:
>
> > Being able to manually define the name can also be useful in some (rare)
> > cases, where you reorganize your project directory tree. But that's not
> > a strong argument for adding this option :-)
>
> Continuing the rationale that rejected the topic from the earlier
> discussion thread, the above is like saying that we should expose
> inode number more to the users and and allow users to tell a
> specific inode number to use when creating an entry in a directory,
> which would allow users to edit the directory with binary editor and
> replace the entry with the same inode number to move or rename the
> path. The discussion considers that the "name" is an implementation
> detail of the worktree subsystem, like inode number is for a
> filesystem implementation. A proper solution would be to invent
> "mv" command ;-).
Hehe :-)
--
Antoine
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-19 19:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 14:47 [PATCH] worktree: add: introduce the --name option Antoine Tenart
2016-07-19 18:04 ` Junio C Hamano
2016-07-19 18:23 ` Duy Nguyen
2016-07-19 18:54 ` Antoine Tenart
2016-07-19 19:04 ` Duy Nguyen
2016-07-19 19:21 ` Eric Sunshine
2016-07-19 19:35 ` Antoine Tenart
2016-07-20 14:54 ` Duy Nguyen
2016-07-20 16:12 ` Antoine Tenart
2016-07-19 18:45 ` Antoine Tenart
2016-07-19 19:08 ` Junio C Hamano
2016-07-19 19:33 ` Antoine Tenart [this message]
2016-07-19 18:52 ` Eric Sunshine
2016-07-20 6:41 ` Antoine Tenart
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=20160719193351.GC28551@kwain \
--to=antoine.tenart@ack.tf \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=sunshine@sunshineco.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).