From: Joshua Jensen <jjensen@workspacewhiz.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Storing notes refs outside of refs/
Date: Thu, 26 Aug 2010 09:02:09 -0600 [thread overview]
Message-ID: <4C7681F1.3070205@workspacewhiz.com> (raw)
Every push to our server creates a note at .git/refs/notes/p4notes
with the equivalent Perforce changelist number, so Git-controlled code
and Perforce-controlled content can stay in sync.
gitk --all and Git Extensions (out of box) show all entries in the
.git/refs/. The p4notes entries are intermixed with the regular branch
content. This creates a HORRID visual mess.
I tried manually moving .git/refs/notes/p4notes to .git/p4/p4notes.
"git log --show-notes=p4/p4notes" fails, but assigning
core.notesDisplayRef=p4/p4notes succeeds.
The best part is, the refs/* namespace is no longer cluttered with junk!
However, "git push origin p4/p4notes:p4/p4notes" fails with the error:
Unable to push to unqualified destination: p4/p4notes. The destination
refspec neither matches an existing ref on the remote nor begins with
refs/, and we are unable to guess a prefix based on the source ref.
Is there a way to make the "git push" work?
Thanks!
Josh
next reply other threads:[~2010-08-26 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 15:02 Joshua Jensen [this message]
2010-08-26 17:05 ` Storing notes refs outside of refs/ 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
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=4C7681F1.3070205@workspacewhiz.com \
--to=jjensen@workspacewhiz.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 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.