Git development
 help / color / mirror / Atom feed
From: Jan Wielemaker <J.Wielemaker@uva.nl>
To: Git Mailing List <git@vger.kernel.org>
Subject: git submodules or, how do we share code between unrelated projects?
Date: Tue, 8 Jul 2008 23:11:32 +0200	[thread overview]
Message-ID: <200807082311.32684.J.Wielemaker@uva.nl> (raw)

Hi,

I'm looking at git-submodule, but I start to get the impression it is old
CVS jargon that brought me there.

We are two open source projects creating implementations of the Prolog
language.  One (SWI-Prolog) is under GIT, the other (YAP) is under CVS
but will move to git if this helps.

We want to start sharing some developments. I guess for each (unrelated)
library we wish to share we must create a git repo, right? Now we
generally need compatibility patches to make this shared code run
on both systems and we need some way to get this code into the main
repo of both systems, such that a clone of the repo of a system gets
you the shared library.

I guess GIT must be perfect for this, but I'm a bit unsure on the
proper setup of the workflow.  Is there a project that has something
similar established and has guidelines how to manage this?

	Cheers --- Jan

                 reply	other threads:[~2008-07-08 21:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200807082311.32684.J.Wielemaker@uva.nl \
    --to=j.wielemaker@uva.nl \
    --cc=git@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox