Re: Using overlay filesystem for "other" files idea

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 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


--
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


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]