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: Mon, 27 Jun 2011 20:56:57 +0200 [thread overview]
Message-ID: <4E08D279.7060202@web.de> (raw)
In-Reply-To: <1309200722.2497.294.camel@Naugrim.eriador.com>
Am 27.06.2011 20:52, schrieb henri GEIST:
> Le lundi 27 juin 2011 à 20:14 +0200, Jens Lehmann a écrit :
>> Am 27.06.2011 18:51, schrieb Junio C Hamano:
>>> One possible working tree organization may look like this:
>>>
>>> -+- lib1
>>> +- project1/Makefile -- refers to ../lib1
>>> +- project2/Makefile -- refers to ../lib1
>>
>> This is what we do at work and it works really well for us. The
>> possible downside (that you can't tie project1 and project2 to a
>> specific version of lib1 in their own repo) is not a real problem
>> in our experience, as the superproject ties the correct combination
>> together.
>>
>
> That is a good starting point.
> I have used this method for some little projects and it work great.
>
> But I had never find a mean to handle the case of project1 depending on
> both lib1 and lib2.
Hmm, but isn't that covered by having lib1, lib2 & project1 right next
to each other in your superproject?
next prev parent reply other threads:[~2011-06-27 19:01 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 [this message]
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
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=4E08D279.7060202@web.de \
--to=jens.lehmann@web$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=henri.geist@flying-robots$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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