git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [RFC] Delete current branch
Date: Fri, 19 Jul 2013 08:08:57 -0700	[thread overview]
Message-ID: <7vr4euy4c6.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CALkWK0=8q4J2yi2to_+41kJSA5E59CBwkG69Hj7MmTPgUnSh5Q@mail.gmail.com> (Ramkumar Ramachandra's message of "Fri, 19 Jul 2013 16:05:04 +0530")

Ramkumar Ramachandra <artagnon@gmail.com> writes:

> Many of my ideas turn out to be really stupid, and I need to throw
> away my feature branch.  So, I find myself doing this often:
>
>   # on branch menuconfig-jk
>   $ git checkout master
>   $ git branch -D<BACKSAPCE>
>   # er, what was the branch name again?
>   $ git checkout -
>   # Ah
>   $ git checkout master
>   $ git branch -D menuconfig-jk
>
> So, I scripted it for myself.  Perhaps we should get the functionality
> in core as `git branch -Dc` (c for "current"; or something)?

What branch will I be on after doing that?  Detached at that branch?

> Also, perhaps a `git describe -` corresponding to `git checkout -`

Did you know that the general way to spell the branch previously you
were on is "@{-1}" and "checkout -" is an ugly special case that is
possible only because "checkout" does not happen to take a "-" as a
valid argument that means something else (like the more usual "read
from standard input")?

Perhaps 

	$ git branch -D @{-1}

would have worked without <BACKSPACE> and everything that follows.

  parent reply	other threads:[~2013-07-19 15:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19 10:35 [RFC] Delete current branch Ramkumar Ramachandra
2013-07-19 14:28 ` Andreas Schwab
2013-07-19 14:35   ` Ramkumar Ramachandra
2013-07-19 15:08 ` Junio C Hamano [this message]
2013-07-19 15:42   ` Ramkumar Ramachandra
2013-07-19 16:48     ` Junio C Hamano
2013-07-19 16:50       ` Ramkumar Ramachandra
2013-07-19 17:08       ` Taylor Hedberg
2013-07-19 19:15         ` Junio C Hamano
2013-07-19 22:52       ` 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:
  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=7vr4euy4c6.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    /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).