From: Jakub Narebski <jnareb@gmail.com>
To: Martin Waitz <tali@admingilde.org>
Cc: git@vger.kernel.org, Josef Weidendorfer <Josef.Weidendorfer@gmx.de>
Subject: Re: Subprojects tasks
Date: Sun, 17 Dec 2006 00:15:23 +0100 [thread overview]
Message-ID: <200612170015.24162.jnareb@gmail.com> (raw)
In-Reply-To: <20061216230108.GE12411@admingilde.org>
Hi!
Martin Waitz wrote:
> On Sat, Dec 16, 2006 at 07:45:11PM +0100, Jakub Narebski wrote:
>>
>> Or .gitlink file, if we decide to implement it (as lightweight checkout and
>> support for submodules which one can easily move/rename).
>
> I still don't get the advantage of a .gitlink file over an ordinary
> repository with alternates or a symlink.
Moving or renaming the directory with a submodule. With alternates,
when you rename or move directory with a submodule, you have to add
alternate for new place / new name, or alter existing alternate.
With symlinks you risk broken symlinks.
When using alternates-like modules file, you can regenerate or
generate "alternates" on checkout, but...
With .gitlink file you can specify GIT_DIR sor submodule as given
directory relative to this directory or one of its parents, so you
can rename and move submodules freely.
P.S. The second (first?) purpose of .gitlink is to be able to have
lightweight checkout, i.e. more than one working area associated with
one repository.
P.P.S. Cc to the author of current .gitlink proposal, to Josef
Weidendorfer.
Message-ID: <200612082252.31245.Josef.Weidendorfer@gmx.de>
http://permalink.gmane.org/gmane.comp.version-control.git/33755
--
Jakub Narebski
next prev parent reply other threads:[~2006-12-16 23:15 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200612170015.24162.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Josef.Weidendorfer@gmx.de \
--cc=git@vger.kernel.org \
--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.
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.