From: Jakub Narebski <jnareb@gmail.com>
To: Martin Waitz <tali@admingilde.org>
Cc: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>,
git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: Re: Subprojects tasks
Date: Sun, 17 Dec 2006 15:29:02 +0100 [thread overview]
Message-ID: <200612171529.03165.jnareb@gmail.com> (raw)
In-Reply-To: <20061217134848.GH12411@admingilde.org>
Martin Waitz wrote:
> On Sun, Dec 17, 2006 at 02:01:09PM +0100, Jakub Narebski wrote:
>> Well, in the .gitlink proposal you could specify GIT_DIR for checkout,
>> or separately: GIT_OBJECT_DIRECTORY, GIT_INDEX_FILE, GIT_REFS_DIRECTORY
>> (does not exist yet), GIT_HEAD_FILE (does not exist yet, and I suppose
>> it wouldn't be easy to implement it). By the way, that's why I'm for
>> .gitlink name for the file, not .git -- this way .gitlink can "shadow"
>> what's in .git, for example specifying in a smart way where to search
>> (where to find) object database, but HEAD and index would be stored
>> together with the checked out directory in .git
>
> What about .git/link or something?
> (Obviously without the capability to change GIT_DIR)
Well, the .gitlink proposal at it is now (by Josef) serves both as a way
to implement lightweight checkout (i.e. having additional working dir to
some repository, or having working dir separate from bare repository),
and as a way to have "smart" submodules (which you can move and rename)
in submodules/subproject support.
Besides, I'd rather either use config file for this (core.link or
core.git_dir), or use .git/GIT_DIR.
>> By the way, I'm rather partial to supermodule following HEAD in submodule,
>> not specified branch. First, I think it is easier from implementation
>> point of view: you don't have to remember which branch supermodule should
>> take submodule commits from; and this cannot be fixed branch name like
>> 'master'.
[...]
> In the setup you described a git-checkout in the supermodule would have
> to switch to a different branch in the submodule, depending on the
> branchname which would have to be stored in the supermodule.
> This a lot more complex.
O.K. Now I understand why you prefer specified branch to HEAD.
I have forgot that checkout must update submodule ref, and if we track HEAD
we would have to remember the branch it pointed to.
By the way, should this ref be in submodule, or in supermodule, e.g. in
refs/modules/<name>/HEAD? And there is a problam _what_ branch should
be that.
Both approaches have advantages and disadvantages...
--
Jakub Narebski
next prev parent reply other threads:[~2006-12-17 14:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 18:32 Subprojects tasks Junio C Hamano
2006-12-16 18:45 ` Jakub Narebski
2006-12-16 23:01 ` Martin Waitz
2006-12-16 23:15 ` Jakub Narebski
2006-12-17 0:01 ` Josef Weidendorfer
2006-12-17 11:45 ` Martin Waitz
2006-12-17 13:01 ` Jakub Narebski
2006-12-17 13:48 ` Martin Waitz
2006-12-17 14:29 ` Jakub Narebski [this message]
2006-12-17 19:54 ` Martin Waitz
2006-12-17 23:27 ` Josef Weidendorfer
2006-12-18 7:45 ` Martin Waitz
2006-12-17 23:23 ` Josef Weidendorfer
2006-12-18 7:44 ` Martin Waitz
2006-12-18 10:30 ` Josef Weidendorfer
2006-12-17 0:08 ` Josef Weidendorfer
2006-12-16 20:35 ` Sven Verdoolaege
2006-12-16 21:07 ` Junio C Hamano
2006-12-16 22:58 ` Martin Waitz
2006-12-16 23:14 ` Sven Verdoolaege
2006-12-17 0:32 ` Josef Weidendorfer
2006-12-17 8:48 ` Alan Chandler
2006-12-17 10:01 ` Jakub Narebski
2006-12-17 11:17 ` Martin Waitz
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200612171529.03165.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Josef.Weidendorfer@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=tali@admingilde.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).