git.vger.kernel.org archive mirror
 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: Wed, 05 Jul 2017 22:56:41 +0530	[thread overview]
Message-ID: <1499275601.16389.6.camel@gmail.com> (raw)
In-Reply-To: <xmqqwp7miztv.fsf@gitster.mtv.corp.google.com>

On Wed, 2017-07-05 at 10:00 -0700, Junio C Hamano wrote:
> Kaartic Sivaraam <kaarticsivaraam91196@gmail.com> writes:
> 
> > So, we're searching for scripts that
> > could both be  helpful to users and could serve as a good sample to
> > prove what could be done using the hooks.
> 
> I am not so sure that we are searching for them, to be honest (who
> are we in this context anyway?)
I think I misinterpreted your sentence in one of the other mails (found
below),

    That sounds like a sample that is there not because it would be
    useful, but because we couldn't think of any useful example.


> This sounds like a solution looking for a problem to me.  The
> simplest option may be to remove the sample hook---perhaps it
> outlived its usefulness.
Removing it is going to be done for sure. I thought it would be even
better to replace it for the reasons I specified previously. Anyways,
in case the last path I sent[1] seems not to be useful and not other
interesting alternatives turn up in this thread then the "simplest
option" has to be chosen.


[1]: http://public-inbox.org/git/20170705165114.20662-1-kaarticsivaraam91196@gmail.com/raw

-- 
Kaartic

  reply	other threads:[~2017-07-05 17:26 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 [this message]
2017-07-05 18:19     ` Kaartic Sivaraam
2017-07-05 19:19       ` Junio C Hamano
2017-07-06  3:28         ` Kaartic Sivaraam

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=1499275601.16389.6.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 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).