From: Jens Lehmann <Jens.Lehmann@web.de>
To: henri GEIST <henri.geist@flying-robots.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: tracking submodules out of main directory.
Date: Tue, 28 Jun 2011 09:37:52 +0200 [thread overview]
Message-ID: <4E0984D0.80506@web.de> (raw)
In-Reply-To: <4E0980D5.8040004@web.de>
Am 28.06.2011 09:20, schrieb Jens Lehmann:
>> This could be a way if .gitmodules can contain something like
>>
>> [module "project one"]
>> path = project1
>> url = ...
>> depends = lib1 "123456"
>> [module "project two"]
>> path = project2
>> url = ...
>> depends = lib1 "abcdef"
>> [module "lib1"]
>> path = lib1
>> url = ...
>
> But there is no need for that as "123456" and "abcdef" are already present
> as the sha1 values for the gitlinks "lib1" and "lib2".
... but of course you would have to decide which sha1 is the right one for
lib1, while your proposal offers two contradicting sha1s (note to self: must
drink coffee *before* answering emails in the morning ;-)
next prev parent reply other threads:[~2011-06-28 7:40 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 13:07 tracking submodules out of main directory henri GEIST
2011-06-27 16:51 ` Junio C Hamano
2011-06-27 18:14 ` Jens Lehmann
2011-06-27 18:52 ` henri GEIST
2011-06-27 18:56 ` Jens Lehmann
2011-06-27 21:18 ` henri GEIST
2011-06-27 19:05 ` Junio C Hamano
2011-06-27 19:40 ` Jens Lehmann
2011-06-27 21:57 ` henri GEIST
2011-06-28 7:25 ` Jens Lehmann
2011-06-28 11:55 ` henri GEIST
2011-06-27 21:51 ` henri GEIST
2011-06-28 7:20 ` Jens Lehmann
2011-06-28 7:37 ` Jens Lehmann [this message]
2011-06-28 11:52 ` henri GEIST
2011-06-28 10:05 ` Alexei Sholik
2011-06-28 17:00 ` Jens Lehmann
2011-07-27 18:49 ` henri GEIST
2011-07-28 8:57 ` henri GEIST
2011-07-28 16:48 ` Jens Lehmann
2011-07-29 9:39 ` henri GEIST
2011-07-30 14:16 ` Jens Lehmann
2011-07-30 21:55 ` henri GEIST
2011-08-01 19:39 ` Jens Lehmann
2011-08-02 12:19 ` henri GEIST
2011-08-02 18:42 ` Jens Lehmann
2011-08-03 6:25 ` Heiko Voigt
2011-08-03 12:26 ` henri GEIST
2011-08-03 17:11 ` Junio C Hamano
2011-08-03 19:07 ` Jens Lehmann
2011-08-03 19:41 ` Junio C Hamano
2011-08-03 21:30 ` Jens Lehmann
2011-08-03 22:29 ` henri GEIST
2011-08-04 17:45 ` Jens Lehmann
2011-08-05 0:29 ` henri GEIST
2011-08-04 20:05 ` Heiko Voigt
2011-08-05 2:19 ` henri GEIST
2011-08-03 21:45 ` Heiko Voigt
2011-08-03 22:41 ` henri GEIST
2011-08-03 21:49 ` henri GEIST
2011-08-03 21:04 ` henri GEIST
2011-08-01 22:12 ` Heiko Voigt
2011-08-02 12:58 ` henri GEIST
[not found] ` <CAJsNXT=93FHjbi42JKA3Pg7PGXs0kEONJ5AC5SSPpa5RSVqB=A@mail.gmail.com>
2011-08-03 9:07 ` henri GEIST
2011-06-27 18:40 ` henri GEIST
2011-06-27 19:02 ` Jens Lehmann
2011-06-27 21:45 ` henri GEIST
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=4E0984D0.80506@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=henri.geist@flying-robots.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 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.