From: Jakub Narebski <jnareb@gmail.com>
To: bdowning@lavos.net (Brian Downing)
Cc: Junio C Hamano <gitster@pobox.com>,
David Symonds <dsymonds@gmail.com>, Bill Lear <rael@zopyra.com>,
Jay Soffian <jaysoffian@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Keeping reflogs on branch deletion
Date: Thu, 14 Feb 2008 08:35:08 -0800 (PST) [thread overview]
Message-ID: <m33arvcx8x.fsf@localhost.localdomain> (raw)
In-Reply-To: <20080214140152.GT27535@lavos.net>
Brian Downing <bdowning@lavos.net> writes:
> When deleting a branch, is there any reason we can't add a deletion
> entry into the reflog and keep the reflog around? This would seem to be
> a lot safer; I know I've been burned by expecting the reflog safety net
> to be there, and surprised that it's not when I've deleted a branch.
There is techical problem with that, namely possibility of D/F
conflict. When you delete branch 'foo', you can later create branch
'foo/bar'. If reflog for 'foo' was not deleted, you couldn't create
reflog for 'foo/bar' because of directory / file conflict.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2008-02-14 16:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 1:39 A couple branch questions Jay Soffian
2008-02-14 1:45 ` David Symonds
2008-02-14 2:24 ` Bill Lear
2008-02-14 3:03 ` David Symonds
2008-02-14 3:43 ` Junio C Hamano
2008-02-14 14:01 ` Keeping reflogs on branch deletion Brian Downing
2008-02-14 15:00 ` Nicolas Pitre
2008-02-14 15:08 ` Johannes Schindelin
2008-02-14 15:17 ` Jeff King
2008-02-14 16:16 ` Nicolas Pitre
2008-02-14 16:31 ` Jeff King
2008-02-14 17:32 ` Nicolas Pitre
2008-02-14 17:57 ` Jeff King
2008-02-14 20:17 ` Wincent Colaiuta
2008-02-14 16:35 ` Jakub Narebski [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=m33arvcx8x.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=bdowning@lavos.net \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@gmail.com \
--cc=rael@zopyra.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;
as well as URLs for NNTP newsgroup(s).