From: Josh Triplett <josh@joshtriplett.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jamey Sharp <jamey@minilop.net>,
"Shawn O. Pearce" <spearce@spearce.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jeff King <peff@peff.net>, Jakub Narebski <jnareb@gmail.com>,
Bert Wesarg <bert.wesarg@googlemail.com>,
git@vger.kernel.org
Subject: [PATCHv10 0/4] ref namespaces
Date: Fri, 8 Jul 2011 16:12:31 -0700 [thread overview]
Message-ID: <cover.1310166525.git.josh@joshtriplett.org> (raw)
This series adds support for dividing the refs of a single repository
into multiple namespaces, each of which can have its own branches, tags,
and HEAD. Git can expose each namespace as an independent repository to
pull from and push to, while sharing the object store, and exposing all
the refs to operations such as git-gc.
Storing multiple repositories as namespaces of a single repository
avoids storing duplicate copies of the same objects, such as when
storing multiple branches of the same source. The alternates mechanism
provides similar support for avoiding duplicates, but alternates do not
prevent duplication between new objects added to the repositories
without ongoing maintenance, while namespaces do.
The first patch improves the prefix handling in the ref iteration
functions, making it possible for us to implement
for_each_namespaced_ref later. The next two patches implement and then
use infrastructure for tracking the current namespace and iterating over
the refs in that namespace. The last patch adds general documentation
for namespaces, and specific references from the documentation on
receive-pack, upload-pack, http-backend, and git.
v10: In receive-pack, add a comment to show_ref_cb documenting the use
of .have refs for refs outside the current namespace. Add the same
comment to the commit message of patch 3.
Josh Triplett (4):
Fix prefix handling in ref iteration functions
ref namespaces: infrastructure
ref namespaces: Support remote repositories via upload-pack and
receive-pack
ref namespaces: documentation
Documentation/Makefile | 2 +-
Documentation/git-http-backend.txt | 8 +++
Documentation/git-receive-pack.txt | 2 +-
Documentation/git-upload-pack.txt | 4 ++
Documentation/git.txt | 13 +++++-
Documentation/gitnamespaces.txt | 75 ++++++++++++++++++++++++++++++++
builtin/receive-pack.c | 40 ++++++++++++++---
cache.h | 3 +
contrib/completion/git-completion.bash | 3 +-
environment.c | 41 +++++++++++++++++
git.c | 18 +++++++-
refs.c | 33 ++++++++++++--
refs.h | 3 +
upload-pack.c | 15 +++---
14 files changed, 236 insertions(+), 24 deletions(-)
create mode 100644 Documentation/gitnamespaces.txt
--
1.7.5.4
next reply other threads:[~2011-07-08 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 23:12 Josh Triplett [this message]
2011-07-08 23:12 ` [PATCHv10 1/4] Fix prefix handling in ref iteration functions Josh Triplett
2011-07-08 23:13 ` [PATCHv10 2/4] ref namespaces: infrastructure Josh Triplett
2011-07-08 23:13 ` [PATCHv10 3/4] ref namespaces: Support remote repositories via upload-pack and receive-pack Josh Triplett
2011-07-08 23:14 ` [PATCHv10 4/4] ref namespaces: documentation Josh Triplett
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1310166525.git.josh@joshtriplett.org \
--to=josh@joshtriplett.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jamey@minilop.net \
--cc=jnareb@gmail.com \
--cc=peff@peff.net \
--cc=spearce@spearce.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).