On Jul 25, 12:39 pm, Tekkub <[email protected]> wrote:
> I would recommend you use git-gui.
Link?
`git commit -a` can be very bad, you
> don't know what you're committing.
When issuing "commit -a", an in-place editor (seems like vi) displays
something that looks like a changelist. I do not know how to issue
command of which files I to commit and I see files that I am certain I
have not edited, and so looking at this stupidly, realizing I am
fumbling.
Plus you're completely skipping one of
> the wonderful features of git, the index (or commit staging area).
I'll have to take your word for it.
> Tekkub
> Github Tech Support
> http://support.github.com/
> Join us on IRC: #github on freenode.net
> Discussion group: [email protected]
>
>
>
> On Sat, Jul 25, 2009 at 1:14 PM, Galaxy <[email protected]> wrote:
>
> > On Jul 25, 11:21 am, Galaxy <[email protected]> wrote:
> > > This should be trivial but I can't seem to figure it out:
>
> > > How do I update files from the github repo?
>
> > > How do I commit changes once I change a file and want to commit that
> > > to the repo?
>
> > > I am using Eclipse to edit and modify files on my local directory.
> > > That much is working just fine. I am fumbling with the GitBash on
> > > windows and the github website.
>
> > I should have added that I have commited in the past, but now I am
> > noticing that "commit -a" command has the effect of opening the in-
> > place editor (vi, I think) with a long list of files that I am pretty
> > sure are untouched. I do not understand what is happening and I do not
> > correctly understand "commit".
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
