git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Chandler <alan@chandlerfamily.org.uk>
To: git@vger.kernel.org
Subject: Re: Looking for SCM that lets me publish part of a repository
Date: Mon, 6 Mar 2006 06:54:12 +0000	[thread overview]
Message-ID: <200603060654.12815.alan@chandlerfamily.org.uk> (raw)
In-Reply-To: <1141608679.16980.12.camel@mattlaptop>

On Monday 06 March 2006 01:31, Matt McCutchen wrote:
> Dear GIT people,
>
> For the last week or so, I have been looking for a SCM system to hold
> many of my projects, some of which are available to the public and
> others of which are not.  It would be nice if I could use a single large
> private repository on my computer with each project in a separate
> folder. 

Not sure why you would want to do this against having lots of smaller 
repositories - (I have lots of small repositories - its mostly java, and my 
shared library files have their own repository which is automatically 
exported to where my projects can access it when I commit to it via a post 
commit hook - you can see the public version of them on my web site) but ...

Create each project on a separate branch of the common repository and ensure 
only the files you want in each project remains on each branch (and any 
shared files can exist in all branches).

In your "remotes" files you list the branches that you want to push to your 
public repository.
-- 
Alan Chandler
http://www.chandlerfamily.org.uk
Open Source. It's the difference between trust and antitrust.

  parent reply	other threads:[~2006-03-06  6:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06  1:31 Looking for SCM that lets me publish part of a repository Matt McCutchen
2006-03-06  1:48 ` Shawn Pearce
2006-03-06  6:54 ` Alan Chandler [this message]
2006-03-06 20:58 ` Sam Vilain

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=200603060654.12815.alan@chandlerfamily.org.uk \
    --to=alan@chandlerfamily.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).