From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Deleting remote branches with git-branch and reflog questions
Date: Tue, 23 Jan 2007 14:12:33 +0100 [thread overview]
Message-ID: <ep51ie$i23$1@sea.gmane.org> (raw)
In-Reply-To: 200701231259.27719.andyparkins@gmail.com
Andy Parkins wrote:
> reflogs
> -------
>
> Why does the reflog directory .git/logs need to store the refs/ directory?
> Aren't /all/ the refs under "refs/" these days?
HEAD is not under refs/. Although IIRC we don't reflog HEAD, with detached
HEAD we could reflog at least detached state.
> Is it right that the reflog for a branch is deleted when the branch is
> deleted? Doesn't this kill one of the advantages of reflogs? In particular,
> if I accidentally deleted a branch, I would have no way of getting it back
> because the reflog has been deleted too? Personally I'd prefer that a reflog
> line was added saying
> XXXXXXXXXXXXXXX 00000000000000 Deleted
> Or similar. After all; it's only disk space. If the ref was later created
> again, then the log can continue to be added to, but it will have a "Created
> from" in the middle instead of at the end.
The problem is when you delete branch 'foo', and then create branch
'foo/bar'. You can't have both 'foo' and 'foo/bar' reflog.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-01-23 13:12 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 [this message]
2007-01-23 14:32 ` Andy Parkins
2007-01-23 14:59 ` Johannes Schindelin
2007-01-23 15:29 ` Andy Parkins
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='ep51ie$i23$1@sea.gmane.org' \
--to=jnareb@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.
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).