From: Evgeniy Ivanov <lolkaantimat@gmail.com>
To: git@vger.kernel.org
Subject: Using overlay filesystem for "other" files idea
Date: Thu, 23 Dec 2010 02:02:00 +0300 [thread overview]
Message-ID: <AANLkTi=f2MXoWE_Dx_thWb3VXGu-V-9cJAC8F_RzGAg=@mail.gmail.com> (raw)
Hello,
I got following idea.
If different branches seriously differ and you switch branches, then
it's more likely you will loose most part of build files (e.g. when
run build).
Also in projects that may have some bugs in build system (e.g. buggy
makefiles) there is a chance you will not get clean build environment.
E.g. somebody forgot to add include file as dependency in Makefile ---
oops, you're in trouble.
Even without bugs in build system, some temp files are overwritten
each time you run build for a custom branch.
I think using overlays for other files can help much to solve this
issue. You can have git repository in regular directory (like now) and
overlay fs mounted over this repository (for each branch its own
overlay).
Another benefit is clearing source tree after build.
What do you think, guys? If it sounds good, I could work on this,
maybe even on my work.
--
Evgeniy Ivanov
next reply other threads:[~2010-12-22 23:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 23:02 Evgeniy Ivanov [this message]
2010-12-23 5:27 ` Using overlay filesystem for "other" files idea Tomas Carnecky
2010-12-23 9:53 ` Evgeniy Ivanov
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='AANLkTi=f2MXoWE_Dx_thWb3VXGu-V-9cJAC8F_RzGAg=@mail.gmail.com' \
--to=lolkaantimat@gmail.com \
--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).