In message <1288037406.819.93.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxx>, Drew Northup
writes:
On Mon, 2010-10-25 at 15:19 -0400, Kynn Jones wrote:
> There are some files that I want to keep under local git
> control, but never push to any remote repositories.
> What's the best way to implement this idea with git?
> The best solution I can think of is to put these files in some
> git-controlled directory that is not below the "main" working
> directory, and have an (ignored) symlink to it in this working
> directory.
> Is there a better way?
There is no restriction that you only have one git repository on any
given machine.... Set up your symlink to those files in their own git
repository.
Depending on your proposed workflow (e.g. do you want to perform many
git operations such as commit, push, pull, tag, branch, etc) on the
public and private repositories at the same time even if they go
different places, a multi-repository management system like gitslave
(http://gitslave.sf.net) might work for you. If you do not plan to
branch/tag your private repository along with the public repository or
do not have an "upstream" for your private repository, the symlink
approach is probably the best.
In either case, remember .git/info/exclude and git-config's
core.excludesfile for a way to privately ignore the symlink or
gitslave files.
-Seth Robertson
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html