Hi,
When i do a git add of a config.h file then make some changes and
then do git commit it does not reflect the changes..
eg
dep@zion:~/programs/elinks/elinks-0.11-20061220$ git add config.h
dep@zion:~/programs/elinks/elinks-0.11-20061220$ vi config.h
dep@zion:~/programs/elinks/elinks-0.11-20061220$ git commit
nothing to commit
dep@zion:~/programs/elinks/elinks-0.11-20061220$ git commit
nothing to commit
dep@zion:~/programs/elinks/elinks-0.11-20061220$ ls
ABOUT-NLS autogen.sh config.h configure debian
INSTALL Makefile.lib SITES TODO
acinclude.m4 BUGS config.h.in configure.in doc
Makefile NEWS src Unicode
aclocal.m4 ChangeLog config.log contrib features.conf
Makefile.config po test
AUTHORS config config.status COPYING features.log
Makefile.config.in README THANKS
dep@zion:~/programs/elinks/elinks-0.11-20061220$
I am working on the hooks part modifying the perl script in the same
in the pre-commit hook but that is not related to this ...
what could be the problem...?
Also another file which you can see in the directory called "NEWS" is
being taken in to consideration...
the hook "pre-commit" is enabled and am adding a spell checker to it...
Regards
Deepak
--
Code Code Code Away
Deepak Barua [off-list ref] wrote:
Hi,
When i do a git add of a config.h file then make some changes and
then do git commit it does not reflect the changes..
eg
dep@zion:~/programs/elinks/elinks-0.11-20061220$ git add config.h
Here you told Git to take the current contents of config.h and
stage it into the index. That content will be in the next
commit.
dep@zion:~/programs/elinks/elinks-0.11-20061220$ vi config.h
Then you modify it. Git doesn't know about those changes to
config.h, nor does it care at this point.
dep@zion:~/programs/elinks/elinks-0.11-20061220$ git commit
nothing to commit
This is occuring because the content staged in the index does not
differ from the content in HEAD (the last commit on this branch).
You need to run `git add config.h` again now that you have modified
it to restage the modified file.
Basically I'm assuming that when you ran `git add config.h` the
first time the content must have matched HEAD, which meant you
didn't actually stage anything.
--
Shawn.
Thank you shawn.
Regards
Deepak
On 1/2/07, Shawn O. Pearce [off-list ref] wrote:
Deepak Barua [off-list ref] wrote:
quoted
Hi,
When i do a git add of a config.h file then make some changes and
then do git commit it does not reflect the changes..
eg
dep@zion:~/programs/elinks/elinks-0.11-20061220$ git add config.h
Here you told Git to take the current contents of config.h and
stage it into the index. That content will be in the next
commit.
quoted
dep@zion:~/programs/elinks/elinks-0.11-20061220$ vi config.h
Then you modify it. Git doesn't know about those changes to
config.h, nor does it care at this point.
quoted
dep@zion:~/programs/elinks/elinks-0.11-20061220$ git commit
nothing to commit
This is occuring because the content staged in the index does not
differ from the content in HEAD (the last commit on this branch).
You need to run `git add config.h` again now that you have modified
it to restage the modified file.
Basically I'm assuming that when you ran `git add config.h` the
first time the content must have matched HEAD, which meant you
didn't actually stage anything.
--
Shawn.
--
Code Code Code Away