# warning in git version 1.6.6.rc0.114.gc8648

3 messages from 2009-12-02 to 2009-12-02. Participants: Alejandro Riveira, Junio C Hamano.
Thread: https://gitlist.dev/t/21827

## Alejandro Riveira, 2009-12-02 17:21

Subject: warning in git version 1.6.6.rc0.114.gc8648
Message-ID: <hf67m0$r10$1@ger.gmane.org>
URL: https://gitlist.dev/e/hf67m0%24r10%241%40ger.gmane.org

```
Whenever i do a "git pull" to check updates to the kernel
or git repo i recieve

warning: 'git merge <msg> HEAD <commit>' is deprecated. Please update
your script to use 'git merge -m <msg> <commit>' instead.
In future versions of git, this syntax will be removed.
Already up-to-date.

git pull should be updated to not use a deprecated form of git merge.

Regards

```

## Junio C Hamano, 2009-12-02 17:50

Subject: Re: warning in git version 1.6.6.rc0.114.gc8648
Message-ID: <7veindgt8v.fsf@alter.siamese.dyndns.org>
URL: https://gitlist.dev/e/7veindgt8v.fsf%40alter.siamese.dyndns.org
In-Reply-To: <hf67m0$r10$1@ger.gmane.org>

```
Alejandro Riveira <ariveira@gmail.com> writes:

> Whenever i do a "git pull" to check updates to the kernel
> or git repo i recieve
>
> warning: 'git merge <msg> HEAD <commit>' is deprecated. Please update
> your script to use 'git merge -m <msg> <commit>' instead.
> In future versions of git, this syntax will be removed.
> Already up-to-date.
>
> git pull should be updated to not use a deprecated form of git merge.

Yes we are aware of the issue and have a patch to do so which requires
another change which we also already have patch for.  It will be fixed
before 1.6.6-rc1

Thanks for reporting.

```

## Alejandro Riveira, 2009-12-02 19:53

Subject: Re: warning in git version 1.6.6.rc0.114.gc8648
Message-ID: <hf6gki$qqu$1@ger.gmane.org>
URL: https://gitlist.dev/e/hf6gki%24qqu%241%40ger.gmane.org
In-Reply-To: <7veindgt8v.fsf@alter.siamese.dyndns.org>

```
El Wed, 02 Dec 2009 09:50:40 -0800, Junio C Hamano escribió:

> Alejandro Riveira <ariveira@gmail.com> writes:
> 
> 
> Yes we are aware of the issue and have a patch to do so which requires
> another change which we also already have patch for.  It will be fixed
> before 1.6.6-rc1

 Thanks for the quick answer :)

> 
> Thanks for reporting.
 
 No; thanks *you* for your work in git ^_^

```