On Tue, Jul 13, 2010 at 11:16:17PM +0200, Remy Bohmer wrote: > What is the intended workflow for the PTXCONF_SETUP_PATCHIN_GIT > developer setting? > I am figuring out how it is supposed to work and if it could (finally) > be used for a workflow like this: > 1) Extract source package > 2) patch sources while building up git-tree > 3) build the tree... > > Now here comes the interesting part: > 4) Developer modifies a source file in the package > 5) 'ptxdist go' starts, but complains about a non-clean tree and maybe > even fails the build, or
this is difficult to do. autogen.sh will also modify files. Or make if the source package is not clean. > 5a) automagically exports the changes to the patches tree, or > 5b) automagically exports only the committed changes to the patches tree... PTXdist master creates a git alias to export the patches: 'git ptx-patches' doing anything automagically is problematic. It will modify patches that didn't really change. mol -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | -- ptxdist mailing list [email protected]
