From: Sascha Cunz <sascha-ml@babbelbox.org>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Bringing a bit more sanity to $GIT_DIR/objects/info/alternates?
Date: Wed, 08 Aug 2012 03:42:11 +0200 [thread overview]
Message-ID: <5037389.HDN2QUVQO5@mephista> (raw)
In-Reply-To: <7vmx2a3pif.fsf@alter.siamese.dyndns.org>
[..]
> - By design, the borrowed object store MUST not ever lose any
> object from it, as such an object loss can corrupt the borrowing
> repositories. In theory, it is OK for the object store whose
> objects are borrowed by repositories to acquire new objects, but
> losing existing objects is an absolute no-no.
[...]
> In practice, this means that users who use "clone -s" to make a
> new repository can *never* prune the original repository without
> risking to corrupt its borrowing repository [*1*].
[...]
Given your example of /git/linux.git being a clone of Linus' repository,
cloning a related repository using it as --reference:
$ cd /git
$ git clone --reference /git/linux.git git://k.org/linux-next.git mine
Wouldn't it be by far a less intrusive alternative to do the following (in the
clone step above):
- create the file /git/linux.git/objects/borrowing/_git_mine (This is where we
borrow FROM).
This file would hold a packed-ref list of HEADs from the /git/mine clone of
the repository.
_git_mine here is slash-stripped version of the destination path. Maybe the
packed-ref format could also be extended by a single line containing a full
path to the foreign repository.
- On every update-ref to /git/mine, update the 'borrowing' refs in
/git/linux.git
- On any maintenance on /git/linux.git (gc, prune, repack, etc.) consider refs
in the packed-refs at objects/borrowing to be valid references.
If packed-ref format was adopted like stated above, we could stat() here if
this directory still exists and error out if it doesn't (In this case the
user should tell us if she moved or removed the clone).
Any alternatives for looking up the packed-refs list for borrowing would also
be doable; i.E. putting the list of valid borrowing-packed-refs-files into the
config file (as opposed to lookup $GIT_DIR/objects/borrowing above).
Putting this list into the config file would eliminate need for the packed-ref
format change and give the user the ability to maintain her clones with well-
known command 'git config'
next prev parent reply other threads:[~2012-08-08 1:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-05 4:56 Bringing a bit more sanity to $GIT_DIR/objects/info/alternates? Junio C Hamano
2012-08-05 9:38 ` Michael Haggerty
2012-08-05 19:01 ` Junio C Hamano
2012-08-07 6:16 ` Jeff King
2012-08-06 21:55 ` Junio C Hamano
2012-08-08 1:42 ` Sascha Cunz [this message]
2012-08-11 9:35 ` Hallvard Breien Furuseth
2012-08-27 22:39 ` Oswald Buddenhagen
2012-08-28 19:19 ` GC of alternate object store (was: Bringing a bit more sanity to $GIT_DIR/objects/info/alternates?) Hallvard Breien Furuseth
2012-08-29 7:42 ` Oswald Buddenhagen
2012-08-29 15:52 ` GC of alternate object store Junio C Hamano
2012-08-30 9:53 ` Oswald Buddenhagen
2012-08-30 16:03 ` Junio C Hamano
2012-08-31 16:26 ` Oswald Buddenhagen
2012-08-31 19:18 ` Dan Johnson
2012-08-31 19:45 ` Junio C Hamano
2012-09-01 4:25 ` [PATCH] fetch --all: pass --tags/--no-tags through to each remote Dan Johnson
2012-09-01 11:22 ` Jeff King
2012-09-01 11:25 ` [PATCH 1/2] argv-array: add pop function Jeff King
2012-09-01 11:27 ` [PATCH 2/2] fetch: use argv_array instead of hand-building arrays Jeff King
2012-09-01 14:34 ` Jens Lehmann
2012-09-01 15:27 ` [PATCH] submodule: " Jens Lehmann
2012-09-01 11:32 ` [PATCH] fetch --all: pass --tags/--no-tags through to each remote Jeff King
2012-09-01 11:34 ` [PATCH 3/2] argv-array: fix bogus cast when freeing array Jeff King
2012-09-05 21:22 ` [PATCHv2] fetch --all: pass --tags/--no-tags through to each remote Dan Johnson
2012-09-07 17:07 ` Junio C Hamano
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=5037389.HDN2QUVQO5@mephista \
--to=sascha-ml@babbelbox.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).