On Tue, Nov 11, 2014 at 2:47 PM, Giorgio Bornia <[email protected]> wrote: > Dear all, > I have a question about how to use git with libmesh. > I want to modify some libmesh files, > so my method is: > - open my own branch, > - start making my changes, > - compile until I get no errors. > > If now I want to make a commit with my changes, > there is a whole bunch of Makefile.in files > (and also some other types of files) > which I do not want to track at all in my commit.
This should only happen if you modified Makefile.am files and reran bootstrap, or ran bootstrap with a different version of the autotools than come with libmesh? > So I thought I would do ' git add ' explicitly only for each file I changed. > > Then my commit would be ' git commit -m "my message" '. > > I wish I could use ' git commit ' with ' -a ' but it seems to me I can't. Don't use -a, that commits all changed files. Just 'git commit' the ones you want to keep, and 'git co' the others to "revert" them. > Do you guys know of any solution > to get rid of all those Makefile.in files > without doing ' git add ' explicitly for each file? Yes, the solution is to not change them in the first place unless you really mean to (in which case you should commit them). So, see my first answer regarding why they might have changed, and then try to avoid doing that if possible. -- John ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
