On 2/26/07, Grant Likely grant.likely@secretlab.ca wrote:
On 2/26/07, Wolfgang Denk wd@denx.de wrote:
There is a strongly established workflow convention use by other git-using projects. The workflow for committing is this: $ git-status # to show what has changed/added/removed $ git-update-index # as needed to update the index $ git-commit # make it real; It should be noted that 'make clean' is not a required step for the commit workflow.
I had a wordy email which boiled down to the above argument, so I'll just agree. Arguing that we should just go with the flow (rather than overcome inertia) by leaving out .gitignore files is assuming that U-Boot is a closed system. :)
There's a *lot* of momentum behind *using* them, and I know every single developer I've talked with (with the notable exception of Wolfgang) has complained on multiple occasions about the uselessness of git status output in U-Boot.
But I'm willing to listen to arguments. At the moment it's that either I have to run an additional command I didn't need to use before, or you have to run "make clean" or use "O=". I don't see any significant difference of added inconvenience between these two. So I tend to shift the inconvenience to you :-)
I second the argument that's already been made the number of people inconvenienced by .gitignore absence is greater than the number inconvenienced by their presence. :-P
Agreed. Our inertia is greater than yours! Join us! ;)
Andy