All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>, Knittl <knittl89@googlemail.com>
Cc: git@vger.kernel.org, Tay Ray Chuan <rctay89@gmail.com>
Subject: Re: [PATCH re-roll] Do not display 'Switched to a new branch' when the branch existed
Date: Wed, 18 Aug 2010 16:38:12 -0700	[thread overview]
Message-ID: <7v4oer8paz.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7voccz8wo8.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Wed\, 18 Aug 2010 13\:59\:03 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> Jonathan Nieder <jrnieder@gmail.com> writes:
>
>> The functionality of your patch is obviously good.  Thanks.
>
> In what way is it good?  I am especially worried about the word "reset"
> being confusing.
>
> You are switching to a new context to work on something else, so I don't
> necessarily think it is confusing that the word "new branch" in this
> message does not mean "a branch that did not exist before this operation
> (i.e. a newly created branch)."

Ahh, please disregard the above; I somehow failed to see that this is only
in the "-b/-B" codepath.  Sorry for the noise.

      reply	other threads:[~2010-08-18 23:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18  8:28 [PATCH] Do not display 'Switched to a new branch' when the branch existed Knittl
2010-08-18  8:38 ` [PATCH re-roll] " Knittl
2010-08-18  9:16   ` Jonathan Nieder
2010-08-18 13:39     ` Tay Ray Chuan
     [not found]       ` <AANLkTimU75krdgQFvw0fEvAPqJb-eKaPXHg_5Hv2A8wh@mail.gmail.com>
2010-08-19  3:21         ` Tay Ray Chuan
2010-08-24  6:50       ` Knittl
2010-08-24 13:06         ` Tay Ray Chuan
2010-08-25 11:51           ` Knittl
2010-08-18 20:59     ` Junio C Hamano
2010-08-18 23:38       ` Junio C Hamano [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:
  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=7v4oer8paz.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=knittl89@googlemail.com \
    --cc=rctay89@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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.