git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] send-email: Refuse to send cover-letter template subject
Date: Fri, 12 Jun 2009 13:48:16 +0200	[thread overview]
Message-ID: <200906121348.19103.trast@student.ethz.ch> (raw)
In-Reply-To: <200906091019.11000.trast@student.ethz.ch>

[-- Attachment #1: Type: Text/Plain, Size: 1516 bytes --]

Thomas Rast wrote:
> Junio C Hamano wrote:
> > Thomas Rast <trast@student.ethz.ch> writes:
> > 
> > > Every so often, someone sends out an unedited cover-letter template.
> > > Add a simple check to send-email that refuses to send if the subject
> > > contains "*** SUBJECT HERE ***", with an option --force to override.
> > 
> > Good ;-).  More valuable to detect would be an empty "blurb" section
> > (i.e. not "unedited *** BLURB HERE ***" string, but literally, there is
> > nothing said in the message other than the shortstat).
> 
> Wouldn't that be AI complete?  As in, whatever regex (or similar) you
> might cook up could probably be matched by *someone's* style of patch
> descriptions, and then it suddenly becomes rather hard to tell them
> apart.

For a contrived example, compare

-- 8< --
Thomas Rast (1):
  Documentation: teach stash/pop workflow instead of stash/apply
-- >8 --

and

-- 8< --
Patch (1):
  Some explanation of what patch number 1 does
-- >8 --

Except for the " (1):", the whole contents of the shortstat are
given by the patches.  So I don't think it's possible to tell them
apart without figuring out what the shortlog would have said for the
actual patches, and comparing that to the contents.  I'd rather not
parse the patches for author info and subject.

What do you want me to do about the patch?  Should I extend it so that
it traps both "*** BLURB HERE ***" and "*** SUBJECT HERE ***"?

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-06-12 11:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08 21:34 [PATCH] send-email: Refuse to send cover-letter template subject Thomas Rast
2009-06-08 23:59 ` Junio C Hamano
2009-06-09  8:19   ` Thomas Rast
2009-06-12 11:48     ` Thomas Rast [this message]
2009-06-12 16:06       ` Junio C Hamano
2009-06-09 18:25   ` Markus Heidelberg
2009-06-09 19:00     ` Junio C Hamano
2009-06-09 19:32       ` Markus Heidelberg

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

  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=200906121348.19103.trast@student.ethz.ch \
    --to=trast@student.ethz.ch \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).