Also, while `git add .` is handy, you may find yourself committing things you don't want committed or didn't know had changed. You might want to use `git status` and commit only the files you worked on. git-gui is also great (albeit ugly) as it will show you what files were changed, and show diffs of *what* was changed in them. On Thu, Jan 15, 2009 at 12:28 PM, Tekkub <[email protected]> wrote:
> Be sure you use `git rm --cached filename` if you don't want the file > deleted from your working copy, only removed from tracking in git. > > > On Thu, Jan 15, 2009 at 12:25 PM, Cynthia Kiser <[email protected]> wrote: > >> >> Quoting sig_UVA <[email protected]>: >> > >> > Thanks! I didn't actually work on that file, but it must be part of >> > the debugging process and gets changed. If I delete it locally and >> > then do the pull, everything works fine. >> > >> > I used "git add ." before my push and commit. It's very convenient; >> > is there a way to do that but exclude that one file that is giving me >> > the problem? I guess the alternative is to just push the files I >> > worked on, but then I might miss something.... >> >> If that file is autogenerated debug info, it should not be committed >> to your repository. I would first do git remove and commit its >> removal. Then add a .gitignore file which lists this file as one to be >> ignored. >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
