All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Jakub Narebski <jnareb@gmail.com>
Subject: Re: Deleting remote branches with git-branch and reflog questions
Date: Tue, 23 Jan 2007 15:29:38 +0000	[thread overview]
Message-ID: <200701231529.40362.andyparkins@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0701231558080.22628@wbgn013.biozentrum.uni-wuerzburg.de>

On Tuesday 2007 January 23 14:59, Johannes Schindelin wrote:

> You mean, kind of like a waste bin? Where you delete stuff, but come back
> and whine that you did not meant to delete it after all?

No, no; I'm whining that the reflog was deleted, not the branch.  I think 
that "ref deleted" is just as valid for logging as anything else, and 
deleting the log makes it impossible to view that operation.

Given how powerful the reflog is; it doesn't seem unreasonable to want to be 
able to do

$ git branch -D some-branch
$ git show some-branch@{2 days ago}




Andy
-- 
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com

      reply	other threads:[~2007-01-23 15:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 12:59 Deleting remote branches with git-branch and reflog questions Andy Parkins
2007-01-23 13:02 ` Andreas Ericsson
2007-01-23 13:14   ` Andy Parkins
2007-01-23 21:25     ` Junio C Hamano
2007-01-23 21:35       ` Johannes Schindelin
2007-01-23 21:52       ` Nicolas Pitre
2007-01-23 22:06         ` Johannes Schindelin
2007-01-24  1:46         ` Junio C Hamano
2007-01-24  2:12           ` Nicolas Pitre
2007-01-24  2:22             ` Jakub Narebski
2007-01-24  3:18               ` Nicolas Pitre
2007-01-24  9:58             ` Johannes Schindelin
2007-01-23 13:12 ` Jakub Narebski
2007-01-23 14:32   ` Andy Parkins
2007-01-23 14:59     ` Johannes Schindelin
2007-01-23 15:29       ` Andy Parkins [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=200701231529.40362.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jnareb@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.