From: Maaartin <grajcar1@seznam.cz>
To: git@vger.kernel.org
Subject: Re: Alternate .gitignore
Date: Fri, 8 Oct 2010 21:39:01 +0000 (UTC) [thread overview]
Message-ID: <loom.20101008T225637-152@post.gmane.org> (raw)
In-Reply-To: AANLkTimG188_8qg-DTtJtvX-wkpotgp7+f8Bu4b4ayMn@mail.gmail.com
Ævar Arnfjörð Bjarmason <avarab <at> gmail.com> writes:
> Have you looked into storing your binaries in a git-submodule(1) ?
I've look at it just now and it doesn't seem to be the thing I need. According
to my very basis understanding submodules seem to be useful for embedding other
projects, but I'm working with a single project only. I'm speaking about a
single project and need to store it in different repositories at different
"ignorance levels".
To make it clear, just imagine that compilation would be many thousand times
slower. In such a case you could prefer to store the history of the *.o files as
well, but you'd still want to avoid the pollution of the source tree. So you'd
maybe use .git for the sources as usually and .git2 (or whatever) for the object
files (maybe together with the sources). This comes very close to my situation.
I could switch to using .git2 using $GIT_DIR, but with "*.o" in my .gitignore I
see no way how to include the ignored files. Maybe I could use $GIT_DIR/info/
exclude somehow instead of .gitignore, but this could be quite cumbersome.
next prev parent reply other threads:[~2010-10-08 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 12:31 Alternate .gitignore Maaartin
2010-10-08 12:45 ` Ævar Arnfjörð Bjarmason
2010-10-08 21:39 ` Maaartin [this message]
2010-10-08 21:45 ` Kevin Ballard
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20101008T225637-152@post.gmane.org \
--to=grajcar1@seznam.cz \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).