From: Damien <email@example.com> To: Junio C Hamano <firstname.lastname@example.org> Cc: email@example.com Subject: Re: [PATCH] run-command.c: add hint when hook is not executable Date: Thu, 5 Oct 2017 22:48:52 +0200 Message-ID: <CAAQ5yihCj2uM00bYO2ipEDkh5mT4F7CwbQ48Fae5XFRebO=nRA@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Wed, Oct 4, 2017 at 6:40 AM, Junio C Hamano <email@example.com> wrote: > Damien <firstname.lastname@example.org> writes: > >> --- > > Please explain why this change makes sense to those who find this > commit in "git log" output six months down the line, without having > read the original thread that motivated you to add this feature > above this line with three dashes. Use your full name on the From: > header of your mail (or alternatively, you can use an in-body "From:" > to override what your MUA places there) and add sign-off with the > same name (cf. Documentation/SubmittingPatches). Thanks, I'm gonna post another version via submitGit. I'm not sure how to send the "cover letter" via submitGit so I'm just gonna explain the patch here and then send it in another message. First, I changed the name of the config to "advice.ignoredHook" since it's more generic and it will allow us to add other cases such as the bad permission case.. > But for the purpose of your patch, you now do care. access(X_OK) > may have failed with EACCESS (i.e. you have no permission to run the > script), in which case your new advise() call may make sense. But > it may have failed with ENOENT or ENOTDIR. And your new advise() > call is a disaster, if the user didn't even have such a hook. For sure, the previous version was really broken. I've now added a EACCES check. But I see two shortcomings left: - the message is shown twice (for a "pre-commit" hook at least) - I tried to take into account the STRIP_EXTENSION case but it's not tested yet > Writing a test would have helped notice this, I would think. You'd > need at least the following variations to cover possibilities: As you will see, I've added tests but my scripting skills are a bit lacking and I used a simple "if...then false else true". I've tried `grep -v` and similar things but this solution is the only one that I found that really works. Thanks for the review, see PATCH in a coming email.
next prev parent reply index Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-03 10:59 Damien 2017-10-04 4:40 ` Junio C Hamano 2017-10-05 20:48 ` Damien [this message] 2017-10-05 20:53 ` [PATCH v2] run-command: add hint when a hook is ignored Damien Marié 2017-10-06 4:52 ` Junio C Hamano 2017-10-06 5:25 ` Junio C Hamano 2017-10-06 5:43 ` Junio C Hamano 2017-10-06 5:53 ` Junio C Hamano 2017-10-06 8:04 ` Damien 2017-10-06 8:07 ` [PATCH v3] " Damien Marié 2017-10-10 4:21 ` Junio C Hamano 2017-10-11 6:26 ` Junio C Hamano 2018-01-03 8:31 ` Jeff King 2018-01-05 19:36 ` Junio C Hamano 2018-03-03 7:16 ` Jeff King 2018-03-05 21:19 ` Junio C Hamano
Reply instructions: You may reply publically 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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAAQ5yihCj2uM00bYO2ipEDkh5mT4F7CwbQ48Fae5XFRebO=nRA@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
firstname.lastname@example.org mailing list mirror (one of many) Archives are clonable: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.org/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ or Tor2web: https://www.tor2web.org/ AGPL code for this site: git clone https://public-inbox.org/ public-inbox