From: Tomas Carnecky <tom@dbservice.com>
To: Evgeniy Ivanov <lolkaantimat@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Using overlay filesystem for "other" files idea
Date: Thu, 23 Dec 2010 06:27:49 +0100 [thread overview]
Message-ID: <4D12DDD5.4050103@dbservice.com> (raw)
In-Reply-To: <AANLkTi=f2MXoWE_Dx_thWb3VXGu-V-9cJAC8F_RzGAg=@mail.gmail.com>
On 12/23/10 12:02 AM, Evgeniy Ivanov wrote:
> 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).
Use ccache.
> 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.
Fix your Makefiles. Or run git clean, see below.
> 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.
git clean -dfx.
Or use two different working trees. See contrib/workdir/git-new-workdir.
tom
next prev parent reply other threads:[~2010-12-23 5:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 23:02 Using overlay filesystem for "other" files idea Evgeniy Ivanov
2010-12-23 5:27 ` Tomas Carnecky [this message]
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=4D12DDD5.4050103@dbservice.com \
--to=tom@dbservice.com \
--cc=git@vger.kernel.org \
--cc=lolkaantimat@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.