On 06/02/15 21:13, Eric Blake wrote: > Chet, > > I've noticed that your 'devel' branch in bash.git is rather messy; > basically lots of commits that snapshot the state of a directory, then a > followup commit that removes leftovers and stray files. If you were to > set your .gitignore file (to make your exclusion list public) or your > .git/info/exclude file (to keep your exclusion list local to your > repository) to the file names that you normally clean up (such as *~, > *.old, *.save, *.orig; one per line), then your imports wouldn't create > those files in the first place, you wouldn't have to do cleanup commits, > and it would be easier to follow the history to see what really changed > without being inundated by all the noise on the side file > creation-deletion loops. >
That would help, but it would be better to have a standard git repo with a commit per change. I understand that existing history can't be converted to a git repo, but that shouldn't preclude pushing standard commits to that git repo from now on. It would really help in verification of bugs/fixes, and would also ease contributions to bash using standard tooling. thanks, Pádraig.
