From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Elena Petrashen <elena.petrashen@gmail.com>,
git@vger.kernel.org, sunshine@sunshineco.com
Subject: Re: [PATCH][Outreachy] branch -D: allow - as abbreviation of @{-1}
Date: Mon, 21 Mar 2016 10:47:49 -0700 [thread overview]
Message-ID: <xmqqtwjzn2nu.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <vpqfuvju4km.fsf@anie.imag.fr> (Matthieu Moy's message of "Mon, 21 Mar 2016 18:24:41 +0100")
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> But I'm not sure how often people want to delete (force-delete according
> to your message) the branch they just come from.
One that I heard was this sequence:
$ git checkout -b work master
$ work work work ...
$ git checkout master
$ git merge work
$ git branch -d work
where their argument was that they are done with the work branch,
and it no longer is needed.
As you may be able to guess, I don't personally subscribe to that
workflow (I'd keep the topic a lot longer, until the result of the
merge is proven to be good in the field), but probably these people
are more perfect developers than I am ;-)
> It might be less
> dangerous to give incentive to the user to spell the branch name
> completely to avoid mistake. As analogy, my shell knows "cd -" but I
> can't "rm -fr -" and I'm happy about it.
That is indeed an interesting analogy.
next prev parent reply other threads:[~2016-03-21 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 15:15 [PATCH][Outreachy] branch -D: allow - as abbreviation of @{-1} Elena Petrashen
2016-03-21 17:24 ` Matthieu Moy
2016-03-21 17:47 ` Junio C Hamano [this message]
2016-03-21 17:56 ` Eric Sunshine
2016-03-21 18:12 ` Junio C Hamano
[not found] ` <CAJPOeMediYQMwvgqhOquVh+KT61gdpUew9ernjuOYuf8By=hZQ@mail.gmail.com>
2016-03-21 19:14 ` Eric Sunshine
2016-03-21 19:27 ` Stefan Beller
2016-03-21 19:26 ` Eric Sunshine
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=xmqqtwjzn2nu.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=elena.petrashen@gmail.com \
--cc=git@vger.kernel.org \
--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 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.