All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Alan Dove <alan.dove@gmail.com>
Subject: Re: Bug: "Received" misspelled in remote message
Date: Thu, 16 Nov 2023 12:42:07 +0900	[thread overview]
Message-ID: <xmqqil62tldc.fsf@gitster.g> (raw)
In-Reply-To: <xmqqmsvetmu3.fsf@gitster.g> (Junio C. Hamano's message of "Thu, 16 Nov 2023 12:10:28 +0900")

Junio C Hamano <gitster@pobox.com> writes:

>> "remote: Recieved update on checked-out branch, queueing deployment."
>>
>> "Received" is misspelled. 
>
> I think it is coming from the "push-to-checkout" hook that is
> installed on your "private server", and not from what we ship as
> part of our software offering.

Googling for the misspelled message seems to indicate that it is
coming from cpanel (whatever it is).  A randomly picked example is
https://essgeelabs.com/posts/cpanel-git-1/ which is a recipe that
does not involve typing the typoed message by the end-user, so
somebody (most likely cPanel) must be shipping with a hook with
typo.

Another user of cPanel reports this

https://forums.cpanel.net/threads/git-automatic-deployment-not-working-but-manual-deployment-is.679837/

where they observe post-receive hook with the typo.

Anybody with contact there at cpanel.net may want to report the bug.

Thanks.

      reply	other threads:[~2023-11-16  3:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15 18:46 Bug: "Received" misspelled in remote message Alan Dove
2023-11-15 19:26 ` Eric Wong
2023-11-15 19:45 ` Konstantin Ryabitsev
2023-11-16  3:10 ` Junio C Hamano
2023-11-16  3:42   ` Junio C Hamano [this message]

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=xmqqil62tldc.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=alan.dove@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.