git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antoine Tenart <antoine.tenart@ack.tf>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Antoine Tenart <antoine.tenart@ack.tf>,
	Git Mailing List <git@vger.kernel.org>,
	Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH] worktree: add: introduce the --name option
Date: Tue, 19 Jul 2016 20:54:52 +0200	[thread overview]
Message-ID: <20160719185452.GB28551@kwain> (raw)
In-Reply-To: <CACsJy8BDRPK2UKxoMat3i2HL38+KFqw2Qfet2Bev26HXRM-BWA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]

On Tue, Jul 19, 2016 at 08:23:58PM +0200, Duy Nguyen wrote:
> On Tue, Jul 19, 2016 at 8:04 PM, Junio C Hamano <gitster@pobox.com> wrote:
> 
> 080739b (worktree.c: find_worktree() search by path suffix -
> 2016-06-13) from 'next' should help identify worktrees in this case by
> specifying 'project0/foo', 'project1/foo'... Granted it's not fun to
> type all that when 'project0/foo' is something long, and bash
> completion probably does not help much either.

So with this I'll be able to create new worktrees, using paths having
the same basename, but in different let's say "project directories"?

> Note that we may need a unique name elsewhere too, e.g.
> refs/worktrees/xyz (even though we haven't settled on this yet). Then
> xyz would be more exposed to the user and an easily recognizable name
> would be a good thing.

Having a recognisable name surely is a good thing, when performing some
(rare) manual operations. Like moving a worktree (or is there a command
for this?)

Thanks,

-- 
Antoine

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-07-19 18:54 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160719185452.GB28551@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.
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).