Alan Chandler <alan@xxxxxxxxxxxxxxxxxxxxx> wrote: [...] > My (albeit limited) experience with using git is at home coding a java > application for my web site using eclipse. During the application > development when I am initially coding the application, or when I am > doing a major update that adds new pages to my site then I have to > remember to git add files. My immediate instinct is do do commands of > the form > > git add > Javasource/uk/org/chandlerfamily/appname/tapestry/pages/subdir/xxx.java > > and > git add Webcontent/subdir/xxx.html > > which even with bash completion is a pain to enter. > > (although that is probably harder than it needs to be - can't I just do > git add . ?) That's different... > I don't know whether we have had the debate here - if we have done it > would have been in the very very early days, but subject to > the .gitignore rules what would be the implications of a git commit -a > that automatically adds any files within the directory (and > subdirectories) in which it is issued. Please don't. It would add e.g. the .class and .o and all ~ files, and all other junk you have lying around (test cases, test run output, ...). It isn't /that/ much more work after creating a new file to record its existence... > I am (at the moment - but I am good at changing my mind) in the side of > giit add for both adding new paths and updating content. This is > purely pragmatic - don't have to remember which one I am trying to do. Me too. It's just a bit weird to use it to register the fact that a file is gone. -- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 2654431 Universidad Tecnica Federico Santa Maria +56 32 2654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 2797513 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html