Re: Importing from tarballs; add, rm, update-index?

From: Alan Chandler <alan@chandlerfamily.org.uk>
Date: Jan 13, 2007, 18:15 UTC
Message-ID: <200701131815.27481.alan@chandlerfamily.org.uk>
In-Reply-To: <E5A7E6A8-45FF-4A7A-A31E-DFEBAD48DF1C@silverinsanity.com>

Show 9 quoted lines

> I was referring to adding Linus' rant...  And maybe several others.
> I tend to find his rants at least slightly amusing, highly
> informative, and I tend to end up agreeing.  I have very little
> opinion on your complaint so long as the system works consistently.
> "git commit -a" is still my most common workflow.  I've used git-add
> (and prior to that git-update-index) from time to time when I fix
> bugs that need to be separate from my current work, but far far more
> common is "I finished this chunk of functionality, add all the
> changes I did to make it happen".

I think the fact that this thread has come alive again implies we didn't bottom it last time through.

One thing, in particular, has been bugging me with the hide the index concept - that is, its still necessary to git add files for them to be picked up with git commit -a

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 . ?)

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.

Then I think you don't even have to get into what is git add all about until you get to the "use the index" stage.

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.

-- 
Alan Chandler
http://www.chandlerfamily.org.uk