git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Christian Couder <christian.couder@gmail.com>,
	git <git@vger.kernel.org>,
	Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
	Thomas Ferris Nicolaisen <tfnico@gmail.com>,
	Nicola Paolucci <npaolucci@atlassian.com>
Subject: Re: Draft of Git Rev News edition 5
Date: Mon, 06 Jul 2015 10:54:28 -0700	[thread overview]
Message-ID: <xmqqfv5118a3.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAPig+cTfkDqSDRqDjA=CNkT1c7Fo0zaLiwi2bAbCLZxPHi5=Bg@mail.gmail.com> (Eric Sunshine's message of "Mon, 6 Jul 2015 13:24:40 -0400")

Eric Sunshine <sunshine@sunshineco.com> writes:

> How about this instead: prefixing with "As originally implemented",
> with a couple s/is/was/ thrown in...
>
>     As originally implemented, creation of linked-worktrees was
>     accomplished via `git checkout --to <path> <branch>`, and cleanup
>     of leftover administrative files, after `<path>` is deleted, was
>     done with `git prune --worktrees`. However, a recent unrelated
>     change to `git prune` led to a discussion that concluded that
>     worktree-related maintenance functionality didn't belong in `git
>     prune`.
>
> Is that sufficient to clue in the reader that "checkout --to" is not
> final form,...

Yeah, I think that is a good way to address my concern.

The current draft release notes to 2.5 mentions this feature as
experimental and warns that its UI is bound to change.  We will
ship the upcoming release with "checkout --to" and the more places
we advise the users that this UI is not final, the better.

  reply	other threads:[~2015-07-06 17:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-05 11:13 Draft of Git Rev News edition 5 Christian Couder
2015-07-05 19:11 ` Eric Sunshine
2015-07-05 21:13   ` Christian Couder
2015-07-05 22:01     ` Eric Sunshine
2015-07-05 22:35       ` Thomas Ferris Nicolaisen
2015-07-05 23:12         ` Eric Sunshine
2015-07-08  7:22           ` Michael J Gruber
2015-07-08  7:43             ` Junio C Hamano
2015-07-08 10:29               ` Christian Couder
2015-07-08 13:02                 ` Johannes Schindelin
2015-07-08 17:36                 ` Junio C Hamano
2015-07-06 16:38   ` Junio C Hamano
2015-07-06 17:24     ` Eric Sunshine
2015-07-06 17:54       ` Junio C Hamano [this message]
2015-07-06 19:39         ` Eric Sunshine
2015-07-06 19:59           ` Christian Couder

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=xmqqfv5118a3.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=npaolucci@atlassian.com \
    --cc=sunshine@sunshineco.com \
    --cc=tfnico@gmail.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).