From: Jeff Garzik <jgarzik@pobox.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: RFC: GIT networked storage
Date: Fri, 04 Nov 2005 15:40:18 -0500 [thread overview]
Message-ID: <436BC732.3090809@pobox.com> (raw)
In-Reply-To: <7vd5lg22gm.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Jeff Garzik <jgarzik@pobox.com> writes:
>
>
>>How easy is it to add a new storage backend to git?
>
>
> Almost everything is contained within sha1_file.c.
>
> Object creation side is simple -- everybody who creates an
> object (e.g update-index registering blobs, write-tree writing
> the toplevel and intermediate level trees, commit-tree building
> a commit object, unpack-objects exploding a pack) goes through
> write_sha1_file(), which checks if the object is already
> available using has_sha1_file() and creates a new object in the
> local .git/objects/?? directory. I am assuming that you are not
> planning to create objects in a remote peer from within the git
> code path, and instead to have background process that replicate
> them over the network to peer repositories, so you probably do
> not have to touch this side.
>
> Extending inspection and reading from existing objects for your
> networked storage may be somewhat messy, but starting points
> are:
[...]
Thanks. It looks pretty straightforward to add a new storage backend,
grepping on the symbols you listed.
Jeff
next prev parent reply other threads:[~2005-11-04 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 4:04 GIT 0.99.9c Junio C Hamano
2005-11-04 4:42 ` RFC: GIT networked storage Jeff Garzik
2005-11-04 9:21 ` Junio C Hamano
2005-11-04 20:40 ` Jeff Garzik [this message]
2005-11-05 14:00 ` GIT 0.99.9c Santi Béjar
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=436BC732.3090809@pobox.com \
--to=jgarzik@pobox.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.