From: kevinr@free-dissociation.com (Kevin Riggle)
Subject: [sup-talk] [PATCH] Add an after-add-message hook
Date: Thu, 20 Aug 2009 22:07:17 -0400 [thread overview]
Message-ID: <1250820245-sup-2250@black-opal.mit.edu> (raw)
In-Reply-To: <1250707991-sup-5429@masanjin.net>
Excerpts from William Morgan's message of Wed Aug 19 14:55:03 -0400 2009:
> Reformatted excerpts from Kevin Riggle's message of 2009-08-18:
> > I don't /think/ so, unless I misunderstand the way hooks work. I
> > assumed the hook would execute and then execution of the loop would
> > resume, and I don't think I throw anything in the hook which should
> > cause that either.
>
> What I'm saying is that this hook will execute *after* each message is
> added to the index, so if Sup found several new messages, all except the
> first one will wait on this hook to execute before being added to the
> index. Or do you mean block in some sense besides "wait for completion"?
Oh, duh. I take your point -- I've sent a new patch.
- Kevin
--
Kevin Riggle (kevinr at free-dissociation.com)
http://free-dissociation.com
prev parent reply other threads:[~2009-08-21 2:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 21:47 Kevin Riggle
2009-08-18 17:56 ` William Morgan
2009-08-18 23:36 ` Kevin Riggle
2009-08-19 18:55 ` William Morgan
2009-08-21 1:57 ` Kevin Riggle
2009-08-24 22:44 ` William Morgan
2009-09-02 13:53 ` William Morgan
2009-08-21 2:07 ` Kevin Riggle [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=1250820245-sup-2250@black-opal.mit.edu \
--to=kevinr@free-dissociation.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