From: Andreas Ericsson <ae@op5.se>
To: git@vger.kernel.org
Subject: Re: Branches and all commits
Date: Mon, 19 Dec 2005 20:32:13 +0100 [thread overview]
Message-ID: <43A70ABD.4090003@op5.se> (raw)
In-Reply-To: <Pine.LNX.4.63.0512191257240.6812@gheavc.wnzcbav.cig>
Jon Nelson wrote:
> On Mon, 19 Dec 2005, Andreas Ericsson wrote:
>
>>>I suspect that the root cause was a 'git branch -D' I issued a while back.
>>>My question is this: if deleting a branch in that manner caused me to enter
>>>this situation, is that a bug or no?
>>
>>It's not a bug. You probably meant to do
>>
>> $ git branch -d
>>
>>-D forces removal even if there are objects reachable only through that
>>branch. The man-page says so, but in git'ish, which isn't always intuitive
>>until you've grown familiar with the glossary.txt doc.
>
>
> I tried 'git branch -d' initially and it refused to delete the branch.
> So I tried 'git branch -D'.
>
> Re-reading your last paragraph makes it clear what happened, then.
> I'll note that I ran 'git branch -D' *days* ago and I've run git-prune
> literally a couple dozen times since then. Is it possible the objects
> weren't removed because they were still referenced by tags?
>
I suppose it must have been, which sort of contradicts how I thought
tags worked. Lucky thing though, eh? :)
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
prev parent reply other threads:[~2005-12-19 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 15:15 Branches and all commits Jon Nelson
2005-12-19 16:15 ` Andreas Ericsson
2005-12-19 17:39 ` Jon Nelson
2005-12-19 17:52 ` Andreas Ericsson
2005-12-19 18:59 ` Jon Nelson
2005-12-19 19:32 ` Andreas Ericsson [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=43A70ABD.4090003@op5.se \
--to=ae@op5.se \
--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 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.