git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [RFC] Light-weight checkouts via ".gitlink"
Date: Fri, 08 Dec 2006 23:18:12 +0100	[thread overview]
Message-ID: <elco6p$uku$1@sea.gmane.org> (raw)
In-Reply-To: 200612082252.31245.Josef.Weidendorfer@gmx.de

A few (very few) comments:

Josef Weidendorfer wrote:

> This can be implemented by enhancing git to ignore any subdirectory which
> has a file .gitlink in it.

If I remember correctly, while git ignores .git, it does not ignore
by default (i.e. without entry in either GIT_DIR/info/excludes, or
.gitignore) the directory which has .git directory in it.

And that should not change for .gitlink. You can always add
.gitignore file with * .* patterns in it (ignore all).
 
> * Gitdir = "<Path to base git repository>"
[...]
> * Name: <explicit name for this checkout>

Why use once "key = value", once "key: value" form? Better to stick
with one. I Would prefer "key = value" one.

GIT_DIR = path to base git repository
it is equivalent to setting the following:

GIT_INDEX_FILE = path to index file
GIT_OBJECT_DIRECTORY = path to object directory
GIT_HEAD_FILE = path to HEAD file
GIT_REFS_DIRECTORY = path to refs directory

NAME = name
should match "name subdirectory" entry in modules file in superproject.


Perhaps instead of adding arbitrary number of .. in front of relative
path, we better use some magic, like ... for finding somewhere up?
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git


  reply	other threads:[~2006-12-08 22:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08 21:52 [RFC] Light-weight checkouts via ".gitlink" Josef Weidendorfer
2006-12-08 22:18 ` Jakub Narebski [this message]
2006-12-08 22:54   ` Josef Weidendorfer
2006-12-08 23:24     ` Jakub Narebski
2006-12-08 23:40       ` Josef Weidendorfer
2006-12-08 23:25     ` Josef Weidendorfer
2006-12-08 23:53       ` Jakub Narebski
2006-12-09  1:46         ` Josef Weidendorfer

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='elco6p$uku$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.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).