From: Tomas Carnecky <tom@dbservice.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Joshua Jensen <jjensen@workspacewhiz.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Storing notes refs outside of refs/
Date: Thu, 26 Aug 2010 20:47:43 +0200 [thread overview]
Message-ID: <4C76B6CF.8040808@dbservice.com> (raw)
In-Reply-To: <7vy6btl2yo.fsf@alter.siamese.dyndns.org>
On 8/26/10 7:05 PM, Junio C Hamano wrote:
> Joshua Jensen <jjensen@workspacewhiz.com> writes:
>
>> I tried manually moving .git/refs/notes/p4notes to .git/p4/p4notes.
>
> Bad idea. Your notes no longer are protected from fsck and prune.
Hm, so storing no longer needed branches outside of the refs/heads
namespace (so that they don't show up in git branch) is a bad idea? This
suggestion was made in #git today or yesterday and I'd like to know if I
should advise people against doing that.
tom
next prev parent reply other threads:[~2010-08-26 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 15:02 Storing notes refs outside of refs/ Joshua Jensen
2010-08-26 17:05 ` Junio C Hamano
2010-08-26 18:25 ` Joshua Jensen
2010-08-26 18:54 ` Junio C Hamano
2010-08-26 19:20 ` Joshua Jensen
2010-08-26 18:47 ` Tomas Carnecky [this message]
2010-08-26 18:51 ` Sverre Rabbelier
2010-08-26 19:09 ` Tomas Carnecky
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=4C76B6CF.8040808@dbservice.com \
--to=tom@dbservice.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jjensen@workspacewhiz.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).