{"thread":{"id":"26126","subject":"Using overlay filesystem for \"other\" files idea","startedAt":"2010-12-22T23:02:00Z","lastAt":"2010-12-23T09:53:01Z","messageCount":3,"participants":["Evgeniy Ivanov","Tomas Carnecky"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"158499","messageId":"AANLkTi=f2MXoWE_Dx_thWb3VXGu-V-9cJAC8F_RzGAg=@mail.gmail.com","threadId":"26126","inReplyTo":null,"subject":"Using overlay filesystem for \"other\" files idea","fromName":"Evgeniy Ivanov","fromEmail":"lolkaantimat@gmail.com","sentAt":"2010-12-22T23:02:00Z","receivedAt":"2010-12-22T23:02:00Z","isPatch":false,"sender":{"key":"lolkaantimat@gmail.com","avatar":null},"body":"Hello,\n\nI got following idea.\n\nIf different branches seriously differ and you switch branches, then\nit's more likely you will loose most part of build files (e.g. when\nrun build).\nAlso in projects that may have some bugs in build system (e.g. buggy\nmakefiles) there is a chance you will not get clean build environment.\nE.g. somebody forgot to add include file as dependency in Makefile ---\noops, you're in trouble.\nEven without bugs in build system, some temp files are overwritten\neach time you run build for a custom branch.\n\nI think using overlays for other files can help much to solve this\nissue. You can have git repository in regular directory (like now) and\noverlay fs mounted over this repository (for each branch its own\noverlay).\nAnother benefit is clearing source tree after build.\n\nWhat do you think, guys? If it sounds good, I could work on this,\nmaybe even on my work.\n\n\n-- \nEvgeniy Ivanov\n"},{"id":"158520","messageId":"4D12DDD5.4050103@dbservice.com","threadId":"26126","inReplyTo":"AANLkTi=f2MXoWE_Dx_thWb3VXGu-V-9cJAC8F_RzGAg=@mail.gmail.com","subject":"Re: Using overlay filesystem for \"other\" files idea","fromName":"Tomas Carnecky","fromEmail":"tom@dbservice.com","sentAt":"2010-12-23T05:27:49Z","receivedAt":"2010-12-23T05:27:49Z","isPatch":false,"sender":{"key":"tom@dbservice.com","avatar":"https://gravatar.com/avatar/900a300bdd1a8bbe086008ad78210bbee2ad2803b7d50a5cba04c1e9404bd6d2?d=mp&s=160"},"body":"  On 12/23/10 12:02 AM, Evgeniy Ivanov wrote:\n> Hello,\n>\n> I got following idea.\n>\n> If different branches seriously differ and you switch branches, then\n> it's more likely you will loose most part of build files (e.g. when\n> run build).\nUse ccache.\n> Also in projects that may have some bugs in build system (e.g. buggy\n> makefiles) there is a chance you will not get clean build environment.\n> E.g. somebody forgot to add include file as dependency in Makefile ---\n> oops, you're in trouble.\nFix your Makefiles. Or run git clean, see below.\n> Even without bugs in build system, some temp files are overwritten\n> each time you run build for a custom branch.\n>\n> I think using overlays for other files can help much to solve this\n> issue. You can have git repository in regular directory (like now) and\n> overlay fs mounted over this repository (for each branch its own\n> overlay).\n> Another benefit is clearing source tree after build.\n\ngit clean -dfx.\n\n\nOr use two different working trees. See contrib/workdir/git-new-workdir.\n\ntom\n"},{"id":"158523","messageId":"AANLkTi=fW+spgi7YYSxEReMk4ZveEt2=Mb_1majKi6GJ@mail.gmail.com","threadId":"26126","inReplyTo":"4D12DDD5.4050103@dbservice.com","subject":"Re: Using overlay filesystem for \"other\" files idea","fromName":"Evgeniy Ivanov","fromEmail":"lolkaantimat@gmail.com","sentAt":"2010-12-23T09:53:01Z","receivedAt":"2010-12-23T09:53:01Z","isPatch":false,"sender":{"key":"lolkaantimat@gmail.com","avatar":null},"body":"Thank you Tom, that's what I wanted.\n\nOn Thu, Dec 23, 2010 at 8:27 AM, Tomas Carnecky <tom@dbservice.com> wrote:\n>  On 12/23/10 12:02 AM, Evgeniy Ivanov wrote:\n>>\n>> Hello,\n>>\n>> I got following idea.\n>>\n>> If different branches seriously differ and you switch branches, then\n>> it's more likely you will loose most part of build files (e.g. when\n>> run build).\n>\n> Use ccache.\n>>\n>> Also in projects that may have some bugs in build system (e.g. buggy\n>> makefiles) there is a chance you will not get clean build environment.\n>> E.g. somebody forgot to add include file as dependency in Makefile ---\n>> oops, you're in trouble.\n>\n> Fix your Makefiles. Or run git clean, see below.\n>>\n>> Even without bugs in build system, some temp files are overwritten\n>> each time you run build for a custom branch.\n>>\n>> I think using overlays for other files can help much to solve this\n>> issue. You can have git repository in regular directory (like now) and\n>> overlay fs mounted over this repository (for each branch its own\n>> overlay).\n>> Another benefit is clearing source tree after build.\n>\n> git clean -dfx.\n>\n>\n> Or use two different working trees. See contrib/workdir/git-new-workdir.\n>\n> tom\n>\n>\n>\n\n\n\n-- \nEvgeniy Ivanov\n"}]}