unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: Sending diffs of `elpa' to the respective maintainers
Date: Tue, 03 Apr 2012 18:06:42 -0400	[thread overview]
Message-ID: <lxk41wbhcd.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <el4nt0tskz.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 03 Apr 2012 17:26:36 -0400")

Glenn Morris wrote:

> (A python fan could probably write a bzr plugin for this.)

For more details, see
http://doc.bazaar.canonical.com/development/en/user-guide/hooks.html

I was thinking of a post_pull hook. Presumably (...) these can access
the list of modified files brought in by a pull, compare the file names
against an external file that maps elpa packages to maintainers, and
send out a "your file has changed" notice. Then someone with a checkout
of the Emacs elpo repo could run bzr pull via cron.

An alternative is to write something that parses the "modified" section
of an emacs-diffs email to extract the file names, then does the same
thing. Invoked via procmail or whatever.



  reply	other threads:[~2012-04-03 22:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 20:38 Sending diffs of `elpa' to the respective maintainers Stefan Monnier
2012-03-21 12:40 ` Stefan Monnier
2012-04-03 20:36 ` Stefan Monnier
2012-04-03 20:52   ` Bastien
2012-04-03 21:26   ` Glenn Morris
2012-04-03 22:06     ` Glenn Morris [this message]
2012-04-28  6:49       ` Glenn Morris
2012-04-28 20:42         ` Stefan Monnier
2012-05-04  6:55           ` Glenn Morris
2012-05-04 18:08             ` Stefan Monnier
2012-05-23  7:41               ` Glenn Morris
2012-05-23 14:28                 ` Stefan Monnier
2012-05-23 16:15                 ` Glenn Morris
2012-05-23 21:56                   ` Glenn Morris

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: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=lxk41wbhcd.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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://git.savannah.gnu.org/cgit/emacs.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).