mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Sunshine <>
To: Junio C Hamano <>
Cc: Git List <>, Duy Nguyen <>
Subject: Re: [PATCH v2] Documentation/git-worktree: fix stale "git checkout --to" references
Date: Thu, 16 Jul 2015 19:26:32 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Jul 16, 2015 at 6:57 PM, Junio C Hamano <> wrote:
> Eric Sunshine <> writes:
>> These should have been changed to "git worktree add" by fc56361
>> (worktree: introduce "add" command, 2015-07-06.
>> Signed-off-by: Eric Sunshine <>
>> ---
> By the way, given the rate of bugs and glitches I am finding in this
> code with a very superficial use in real work only for a few days,
> perhaps we would want to add a warning to the documentation of "git
> worktree", in addition to the "this is still experimental" mention
> in the release notes, to discourage people to keep their only copy
> of the work in a secondary worktree for now?
>  ----
> -Multiple checkout support for submodules is incomplete. It is NOT
> -recommended to make multiple checkouts of a superproject.
> +Multiple checkout in general is still experimental, and the support
> +for submodules is incomplete. It is NOT recommended to make multiple
> +checkouts of a superproject.

Maybe, maybe not.

The submodule item is at least (hopefully) quantitative. That is,
there should be some point after specific shortcomings have been
addressed when we can say "submodules are now supported", and remove
the item from BUGS.

But, "in general is still experimental" is nebulous and open-ended. At
what point do we stop considering it experimental, and who will
remember to remove the entry from BUGS when that day comes?

Other than that concern, the revised text seems reasonable.

      reply	other threads:[~2015-07-16 23:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 22:09 [PATCH v2] Documentation/git-worktree: fix stale "git checkout --to" references Eric Sunshine
2015-07-16 22:57 ` Junio C Hamano
2015-07-16 23:26   ` Eric Sunshine [this message]

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:

  List information:

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

  git send-email \
    --in-reply-to='' \ \ \ \ \

* 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

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