All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Strickroth <sven.strickroth@tu-clausthal.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: RFC: reflog for deleted branches
Date: Fri, 04 May 2012 00:10:56 +0200	[thread overview]
Message-ID: <4FA30270.6000806@tu-clausthal.de> (raw)
In-Reply-To: <7vaa1pdjz8.fsf@alter.siamese.dyndns.org>

Am 03.05.2012 23:37 schrieb Junio C Hamano:
> The itch is legit, but I doubt a "special log for deleted branches" is a
> good design.  Why do you limit yourself only to a single "last" commit?

That was just the first idea ;)

> Wouldn't it be a better design to save away the entire reflog for the
> branch when a branch is deleted, possibly with expedited expire rule for
> such a reflog?

The "normal" reflog cannot be used if you just create and then delete a
branch - the reflog is empty in this case. A special "deleted" entry
pointing to the SHA1 of the branch is needed. Also the question is how
to handle the case that a user creates and deletes a new branch with the
same name.

All in all, I (and lots of other users) would be happy if this issue
could be addressed in one of the next releases. :)

-- 
Best regards,
 Sven Strickroth
 ClamAV, a GPL anti-virus toolkit   http://www.clamav.net
 PGP key id F5A9D4C4 @ any key-server

  reply	other threads:[~2012-05-03 22:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03 21:25 RFC: reflog for deleted branches Sven Strickroth
2012-05-03 21:37 ` Junio C Hamano
2012-05-03 22:10   ` Sven Strickroth [this message]
2012-05-03 23:05     ` Junio C Hamano
2012-05-03 23:39       ` Sven Strickroth
2012-05-04  6:27       ` Robin Rosenberg
2012-05-04 16:24         ` Junio C Hamano
2012-05-03 22:13 ` Andrew Sayers
2012-05-04  1:17 ` Sitaram Chamarty

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=4FA30270.6000806@tu-clausthal.de \
    --to=sven.strickroth@tu-clausthal.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.