Git ignore has worked well so far, but I am going to try the git gui now. Sounds interesting.
On Jan 15, 8:41 pm, Sitaram Chamarty <[email protected]> wrote: > On Fri, Jan 16, 2009 at 1:01 AM, Tekkub <[email protected]> wrote: > > 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. > > For the problem described below, "git gui" after "git add ." actually works > very well -- just pick the files you don't want to commit from the bottom left > pane and click the icon next to it, it moves to the top left pane, which is > "unstaged". > > Of course, in the general case it's better to gitignore this file if it's > being generated by some software, as others have said > > Regards, > > Sitaram > > > On Thu, Jan 15, 2009 at 12:28 PM, Tekkub <[email protected]> wrote: > >> On Thu, Jan 15, 2009 at 12:25 PM, Cynthia Kiser <[email protected]> wrote: > >>> Quoting sig_UVA <[email protected]>: > >>> > 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 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
