mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Stefan Beller <>
To: Jonathan Nieder <>
Cc: Junio C Hamano <>,
	"" <>
Subject: Re: [PATCH] checkout: do not mention detach advice for explicit --detach option
Date: Wed, 10 Aug 2016 15:46:11 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Aug 10, 2016 at 10:32 AM, Jonathan Nieder <> wrote:
> Stefan Beller wrote:
>> When a user asked for a detached HEAD specifically with `--detach`,
>> we do not need to give advice on what a detached HEAD state entails as
>> we can assume they know what they're getting into as they asked for it.
> Example? Tests?

There are no tests for the advice things IIUC.
What do you mean by example?


  reply	other threads:[~2016-08-10 22:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 17:28 [PATCH] checkout: do not mention detach advice for explicit --detach option Stefan Beller
2016-08-10 17:32 ` Jonathan Nieder
2016-08-10 22:46   ` Stefan Beller [this message]
2016-08-11 18:09     ` Junio C Hamano
2016-08-10 18:00 ` Junio C Hamano

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