git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Antoine Tenart <antoine.tenart@ack.tf>
Cc: git@vger.kernel.org, pclouds@gmail.com, sunshine@sunshineco.com
Subject: Re: [PATCH] worktree: add: introduce the --name option
Date: Tue, 19 Jul 2016 12:08:11 -0700	[thread overview]
Message-ID: <xmqqh9blfntw.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160719184510.GA28551@kwain> (Antoine Tenart's message of "Tue, 19 Jul 2016 20:45:10 +0200")

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 ;-).


  reply	other threads:[~2016-07-19 19:08 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 [this message]
2016-07-19 19:33       ` Antoine Tenart
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=xmqqh9blfntw.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=antoine.tenart@ack.tf \
    --cc=git@vger.kernel.org \
    --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).