Are "private blobs/trees" possible?

Are "private blobs/trees" possible?

[Kynn Jones]

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?

TIA!

~kj

Re: Are "private blobs/trees" possible?

[Drew Northup]

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?
> 
> TIA!

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.

-- 
-Drew Northup N1XIM
   AKA RvnPhnx on OPN
________________________________________________
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59

Re: Are "private blobs/trees" possible?

[Seth Robertson]

In message <1288037406.819.93.camel@drew-northup.unet.maine.edu>, 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

Re: Are "private blobs/trees" possible?

[Kynn Jones]

Actually, it occurred to me after posting that the symlinking is not
necessary.  As long as the private directory is ignored, then it can
have its own independent (and purely local) git repository.

But I'll look into the multi-repo management system that Seth mentioned.

Thanks!