From: Johan Herland <johan@herland•net>
To: git@vger•kernel.org
Cc: Junio C Hamano <gitster@pobox•com>,
Shawn Pearce <spearce@spearce•org>, Kenny Root <kroot@google•com>,
Jonathan Nieder <jrnieder@gmail•com>,
Thomas Rast <trast@student•ethz.ch>
Subject: Re: [PATCH] Remove restriction on notes ref base
Date: Tue, 02 Nov 2010 23:58:11 +0100 [thread overview]
Message-ID: <201011022358.11340.johan@herland.net> (raw)
In-Reply-To: <7vsjzj1v49.fsf@alter.siamese.dyndns.org>
On Tuesday 02 November 2010, Junio C Hamano wrote:
> As to remote interface, refs/remotes/$remotes/ hierarchy corresponds to
> the local refs/heads/ interface, so I do not think we will change the
> default mapping we document (and have "clone" prepare) to place notes
> obtained from elsewhere in refs/remotes/ hierarchy (we do not do that for
> tags neither), so I think Johan's point is an independent issue.
I assume that means you'd rather have remote-tracking notes refs live under
refs/notes. So, to avoid collisions with local notes refs (and remote-
tracking notes refs from _other_ remote), we probably want to store them
under refs/notes/remotes/$remote/. I have no problem with that.
Although I'm starting to wonder whether our remote -> local refspec mappings
are getting too varied (i.e. confusing). Currently we have:
Remote repo -> Local repo
------------------------------------------------
refs/heads/* refs/remotes/$remote/*
refs/tags/* refs/tags/*
...and soon we may also have:
refs/notes/* refs/notes/remotes/$remote/*
Of these, the first is specified in the config, the second is
implicit/magic, and the third would be specified in the config.
...Johan
--
Johan Herland, <johan@herland•net>
www.herland.net
next prev parent reply other threads:[~2010-11-02 22:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 0:16 [PATCH] Remove restriction on notes ref base Kenny Root
2010-11-02 6:52 ` Jonathan Nieder
2010-11-02 8:48 ` Johan Herland
2010-11-02 14:11 ` Shawn Pearce
2010-11-02 14:29 ` Jeff King
2010-11-02 15:24 ` Johan Herland
2010-11-02 17:41 ` Junio C Hamano
2010-11-02 22:58 ` Johan Herland [this message]
2010-11-02 23:28 ` Chris Forbes
2010-11-03 6:41 ` Jonathan Nieder
2010-11-03 16:17 ` Junio C Hamano
2010-11-03 16:30 ` Sverre Rabbelier
2010-11-04 0:49 ` Johan Herland
2010-11-04 1:00 ` Sverre Rabbelier
2010-11-04 14:35 ` Tag refspecs (was Re: [PATCH] Remove restriction on notes ref base) Marc Branchaud
2010-11-05 1:02 ` Johan Herland
2010-11-05 15:11 ` Marc Branchaud
2010-11-04 14:58 ` [PATCH] Remove restriction on notes ref base Jeff King
2010-11-05 1:29 ` Johan Herland
2010-11-05 14:55 ` Jeff King
2010-11-03 16:35 ` Jonathan Nieder
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=201011022358.11340.johan@herland.net \
--to=johan@herland$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=jrnieder@gmail$(echo .)com \
--cc=kroot@google$(echo .)com \
--cc=spearce@spearce$(echo .)org \
--cc=trast@student$(echo .)ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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