git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Ignore BASE extension
Date: Fri, 13 Apr 2007 12:43:20 -0700	[thread overview]
Message-ID: <7vslb4awmf.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200704131233.13979.andyparkins@gmail.com> (Andy Parkins's message of "Fri, 13 Apr 2007 12:33:12 +0100")

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.

  reply	other threads:[~2007-04-13 19:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13 11:33 Ignore BASE extension Andy Parkins
2007-04-13 19:43 ` Junio C Hamano [this message]
2007-04-13 19:57   ` Andy Parkins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vslb4awmf.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).