All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Requesting suggestions for a good sample "prepare-commit-msg" hook
Date: Thu, 06 Jul 2017 08:58:12 +0530	[thread overview]
Message-ID: <1499311692.1776.3.camel@gmail.com> (raw)
In-Reply-To: <xmqqzicihesv.fsf@gitster.mtv.corp.google.com>

On Wed, 2017-07-05 at 12:19 -0700, Junio C Hamano wrote:
> I honestly do not see your point.  Yes, I said that the change
> indicates that there is no useful example found (so far).  That does
> not necessarily mean that we must find a useful example so that we
> can keep this sample script, which now became useless, alive.  
> 
> I am questioning the assumption that it helps users to have a sample
> for prepare-commit-msg shipped with our source, and I suspect that
> it may no longer be true.  If the sole purpose of finding a useful
> example is to keep the sample script alive, when the sample script
> is no longer a useful thing to ship, then it does sound like "a
> solution looking for a problem", no?
> 
Ah, now I see your point. When you said "it's no longer useful", I
thought you were mentioning only the part of the script that commented
the sign-off. Now I get that your point of not shipping the sample
script itself. Now that clears the confusion and sorry for the
confusion I may have caused.

-- 
Kaartic

      reply	other threads:[~2017-07-06  3:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 16:45 Requesting suggestions for a good sample "prepare-commit-msg" hook Kaartic Sivaraam
2017-07-05 17:00 ` Junio C Hamano
2017-07-05 17:26   ` Kaartic Sivaraam
2017-07-05 18:19     ` Kaartic Sivaraam
2017-07-05 19:19       ` Junio C Hamano
2017-07-06  3:28         ` Kaartic Sivaraam [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=1499311692.1776.3.camel@gmail.com \
    --to=kaarticsivaraam91196@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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.