Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Karl Hasselström" <kha@treskal.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 3/3] Make old sha1 optional with git update-ref -d
Date: Mon, 26 May 2008 11:51:12 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.1.00.0805261149310.30431@racer> (raw)
In-Reply-To: <20080525161440.25087.83011.stgit@yoghurt>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 518 bytes --]

Hi,

On Sun, 25 May 2008, Karl Hasselström wrote:

> Giving the old sha1 is already optional when changing a ref, and it's
> quite handy when running update-ref manually. So make it optional for
> deleting a ref too.

Isn't this a bit dangerous, especially given that there is potentially 
_no_ reflog as a safeguard?

So no, it is not the same as when changing a ref.

I am mildly negative on this (having lost some remote branches, because 
they were deleted _together with the reflogs_ by "git push bla :x"),
Dscho

  reply	other threads:[~2008-05-26 10:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-25 16:14 [PATCH 0/3] Make old sha1 optional with git update-ref -d Karl Hasselström
2008-05-25 16:14 ` [PATCH 1/3] Add some tests for " Karl Hasselström
2008-05-25 16:14 ` [PATCH 2/3] Clean up builtin-update-ref's option parsing Karl Hasselström
2008-05-25 18:40   ` Junio C Hamano
2008-05-25 19:32     ` Karl Hasselström
2008-06-02 23:34       ` [PATCH v2 0/2] Make old sha1 optional with git update-ref -d Karl Hasselström
2008-06-02 23:34         ` [PATCH v2 1/2] Clean up builtin-update-ref's option parsing Karl Hasselström
2008-06-02 23:34         ` [PATCH v2 2/2] Make old sha1 optional with git update-ref -d Karl Hasselström
2008-06-03  5:51           ` Junio C Hamano
2008-06-03  6:49             ` Karl Hasselström
2008-06-03 19:39               ` Junio C Hamano
2008-05-25 16:14 ` [PATCH 3/3] " Karl Hasselström
2008-05-26 10:51   ` Johannes Schindelin [this message]
2008-05-26 14:09     ` Karl Hasselström

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=alpine.DEB.1.00.0805261149310.30431@racer \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kha@treskal.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox