Ignore BASE extension

Ignore BASE extension

[Andy Parkins]

Hello,

$ git --version
git version 1.5.1.1.83.g2bfe3

I've just compiled the latest version from master; and started getting 
this message

$ git add foo.c
Ignore BASE extension

What does that mean?  Should I be concerned?



Andy
-- 
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com

Re: Ignore BASE extension

[Junio C Hamano]

Andy Parkins <andyparkins@gmail.com> writes:

> Hello,
>
> $ git --version
> git version 1.5.1.1.83.g2bfe3
>
> I've just compiled the latest version from master; and started getting 
> this message
>
> $ git add foo.c
> Ignore BASE extension
>
> What does that mean?  Should I be concerned?

The message would have said "ignoring BASE extension", but this
means you used git from 'next' to update your index and HEAD and
then are now running 'git add' from 'master' or older that does
not have the support for BASE extension.

For description of what BASE extension does, look at log
messages between master..a640e62, especially 0679f9ac.

The notice is harmless.  Any extension data section that the
index file can have, whose name begins with a capital letter
(like 'B'), is meant to be ignorable.  They enhance
functionality or improve performance if understood, but an older
tool that does not understand them can safely ignore and
correctly operate.

Another extension, by the way, is TREE extension, which holds
the cache-tree to speed up write-tree operation.  I think
everybody's git would understand them by now.

Re: Ignore BASE extension

[Andy Parkins]

On Friday 2007, April 13, Junio C Hamano wrote:

> The message would have said "ignoring BASE extension", but this
> means you used git from 'next' to update your index and HEAD and
> then are now running 'git add' from 'master' or older that does
> not have the support for BASE extension.

I can't quite remember what I did, but I could easily have been 
running 'next' from last week and then today's 'master'.  Regardless, 
everything seems fine and the message has now vanished.  Thanks for the 
reassurance that no data was in danger.


Andy

-- 
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com