From: Alexander Litvinov <lan@ac-sw.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
git@vger.kernel.org, Petr Baudis <pasky@suse.cz>
Subject: Re: Notes on Subproject Support
Date: Mon, 23 Jan 2006 12:06:53 +0600 [thread overview]
Message-ID: <200601231206.53466.lan@ac-sw.com> (raw)
In-Reply-To: <7v64ob1omh.fsf@assigned-by-dhcp.cox.net>
In our development we use a little bit other case (it is simplified):
1. We have self written C++ library for linked list implementation. Lets call
it liblist.
2. We have project A that use liblist as separate directory and project B that
use this library too.
Currently we have 3 cvs projects with cvs-modules for linking liblist to A and
B. During development of A and B we often modify liblist to fix bugs and
these changes are immidatly visible to all projects who use liblist.
After full implementation of bind functionality I see one restriction: I have
to use one repo for storing all three projects: A, B and liblist to make
changes of liblist visible to all projects. The solution is to make separate
repos and on each change of liblist in prokect A push these changes to
liblist repo and pull them into project B again - bit hacky solution.
next prev parent reply other threads:[~2006-01-23 6:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 1:35 Notes on Subproject Support Junio C Hamano
2006-01-23 3:50 ` Daniel Barkalow
2006-01-23 4:36 ` Junio C Hamano
2006-01-23 5:48 ` Junio C Hamano
2006-01-23 6:06 ` Alexander Litvinov [this message]
2006-01-23 16:48 ` Daniel Barkalow
2006-01-23 8:38 ` Junio C Hamano
2006-01-23 17:57 ` Daniel Barkalow
2006-01-24 1:50 ` Junio C Hamano
2006-01-23 16:31 ` Daniel Barkalow
2006-01-24 1:50 ` Junio C Hamano
2006-01-24 4:22 ` Daniel Barkalow
2006-01-23 8:00 ` Junio C Hamano
2006-01-23 12:50 ` Martin Atukunda
2006-01-23 19:30 ` Junio C Hamano
2006-01-28 4:55 ` Horst von Brand
2006-01-28 21:43 ` Junio C Hamano
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=200601231206.53466.lan@ac-sw.com \
--to=lan@ac-sw.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pasky@suse.cz \
/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.