From: Jamey Sharp <jamey@minilop.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jeff King <peff@peff.net>, Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org
Subject: [PATCHv6 0/4] Support ref namespaces
Date: Fri, 3 Jun 2011 17:11:39 -0700 [thread overview]
Message-ID: <1307146303-4524-1-git-send-email-jamey@minilop.net> (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 is a bugfix; it's important regardless, but we need it
to correctly 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.
v6 improves the commit message in patch 2/4, and the documentation in 4/4,
regarding why namespaces treat '/' specially.
Jamey Sharp and Josh Triplett (4):
Fix prefix handling in ref iteration functions
Add infrastructure for ref namespaces
Support ref namespaces for remote repositories via upload-pack and
receive-pack
Add documentation for ref namespaces
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 | 34 ++++++++++++---
cache.h | 3 +
contrib/completion/git-completion.bash | 3 +-
environment.c | 41 +++++++++++++++++
git.c | 18 +++++++-
refs.c | 27 +++++++++++-
refs.h | 3 +
upload-pack.c | 15 +++---
14 files changed, 227 insertions(+), 21 deletions(-)
create mode 100644 Documentation/gitnamespaces.txt
--
1.7.5.3
next reply other threads:[~2011-06-04 0:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 0:11 Jamey Sharp [this message]
2011-06-04 0:11 ` [PATCHv6 1/4] Fix prefix handling in ref iteration functions Jamey Sharp
2011-06-04 0:11 ` [PATCHv6 2/4] Add infrastructure for ref namespaces Jamey Sharp
2011-06-04 0:11 ` [PATCHv6 3/4] Support ref namespaces for remote repositories via upload-pack and receive-pack Jamey Sharp
2011-06-04 0:11 ` [PATCHv6 4/4] Add documentation for ref namespaces Jamey Sharp
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=1307146303-4524-1-git-send-email-jamey@minilop.net \
--to=jamey@minilop.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
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).