From: Junio C Hamano <gitster@pobox.com>
To: Alejandro Riveira <ariveira@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: warning in git version 1.6.6.rc0.114.gc8648
Date: Wed, 02 Dec 2009 09:50:40 -0800 [thread overview]
Message-ID: <7veindgt8v.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <hf67m0$r10$1@ger.gmane.org> (Alejandro Riveira's message of "Wed\, 2 Dec 2009 17\:21\:04 +0000 \(UTC\)")
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.
next prev parent reply other threads:[~2009-12-02 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 17:21 warning in git version 1.6.6.rc0.114.gc8648 Alejandro Riveira
2009-12-02 17:50 ` Junio C Hamano [this message]
2009-12-02 19:53 ` Alejandro Riveira
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=7veindgt8v.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=ariveira@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).