From: Luciano Rocha <luciano@eurotux.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: relative objects/info/alternates
Date: Sat, 15 Dec 2007 07:39:40 +0000 [thread overview]
Message-ID: <20071215073940.GA22118@bit.office.eurotux.com> (raw)
In-Reply-To: <m3bq8tqs9c.fsf@roke.D-201>
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
On Fri, Dec 14, 2007 at 06:13:09AM -0800, Jakub Narebski wrote:
> Luciano Rocha <luciano@eurotux.com> writes:
>
> > Can I use relative $GIT_DIR/objects/info/alternates? Will the git
> > commands work anywhere inside the working-copy despice the alternate
> > being relative to the root of it?
>
> From the information in repository layout documentation:
>
> objects/info/alternates::
> This file records paths to alternate object stores that
> this object store borrows objects from, one pathname per
> line. Note that not only native Git tools use it locally,
> but the HTTP fetcher also tries to use it remotely; this
> will usually work if you have relative paths (relative
> to the object database, not to the repository!) in your
> alternates file, but it will not work if you use absolute
> paths unless the absolute path in filesystem and web URL
> is the same. See also 'objects/info/http-alternates'.
>
> it looks like you can have relative paths in alternates.
It doesn't work too well, when a tree with relative alternat is used by
another:
error: ./objects/../../2.6.23.y.git/objects: ignoring relative
alternate object store ../../linus.git/objects
--
Luciano Rocha <luciano@eurotux.com>
Eurotux Informática, S.A. <http://www.eurotux.com/>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-12-15 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 14:06 relative objects/info/alternates Luciano Rocha
2007-12-14 14:13 ` Jakub Narebski
2007-12-15 7:39 ` Luciano Rocha [this message]
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=20071215073940.GA22118@bit.office.eurotux.com \
--to=luciano@eurotux.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).