All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
	Elena Petrashen <elena.petrashen@gmail.com>,
	Git List <git@vger.kernel.org>
Subject: Re: [PATCH][Outreachy] branch -D: allow - as abbreviation of @{-1}
Date: Mon, 21 Mar 2016 11:12:40 -0700	[thread overview]
Message-ID: <xmqqegb3n1if.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: CAPig+cQNBeBaLb-znNgxOanUz++pQLae=c8vUtFXjqxOns4d-g@mail.gmail.com

Eric Sunshine <sunshine@sunshineco.com> writes:

> On Mon, Mar 21, 2016 at 1:47 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> 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.
>
> I frequently use throwaway branches when messing around with some idea
> or when reviewing patches submitted to the mailing list, and the
> workflow ends up being similar to the above:
>
>     $ git checkout -b throwaway master
>     $ ...work work work...
>     $ git checkout master
>     $ git branch -D throwaway
>
> So, I can see how having "git branch -D" (force-delete) recognize "-"
> could be a convenience.

I guess that it would make some sense in ancient world, but there is
detached HEAD for that workflow, so it is unlikely that I'd find it
useful myself (in my worldview, throw-away work is discardable by
default, which is why I start from detached HEAD, until I find that
the result is more interesting than I originally thought and decide
to save it to a more permanent branch with "checkout -b" from
there).

But of course people are different.

In any case, we found two plausible explanation why people may want
to do this.  I however tend to agree with Matthieu that it may be
safer not to give a short-hand access to destructive operations.

  reply	other threads:[~2016-03-21 18:12 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
2016-03-21 17:56     ` Eric Sunshine
2016-03-21 18:12       ` Junio C Hamano [this message]
     [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=xmqqegb3n1if.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.