unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bastien <bastienguerry@googlemail.com>
Cc: Glenn Morris <rgm@gnu.org>, Juanma Barranquero <lektu@terra.es>,
	Miles Bader <miles@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: org changes lost
Date: Tue, 25 Nov 2008 10:33:47 +0100	[thread overview]
Message-ID: <0D52CA63-7E8D-474F-8DDA-F64278A85801@gmail.com> (raw)
In-Reply-To: <87r650yy6y.fsf@gnu.org>

Hi Bastien,

I would appreciate this service, thank you very much.

- Carsten

On Nov 25, 2008, at 10:03 AM, Bastien wrote:

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> For me the biggest improvement would be to get an email copy
>>> of all changes to files where I am the maintainer, not buried
>>> in the general commits digest (where I do overlook things),
>>> but a personalized one. I am sure that such emails could be
>>> generated automatically, but I don't know how.
>>
>> That would be good indeed.  Maybe someone could setup such a service:
>> register to emacs-diffs, and then use a table that maps file names to
>> maintainers's email addresses to figure out to whom to send the  
>> email.
>
> I've set up such a system.
>
> Carsten, if you're okay with this, I can automatically forward
> org-related emails from [emacs-commit] and [emacs-diffs] to you.
>
> I've not done this for all Emacs projects so far, partly because the
> MAINTAINERS file might not be 100% accurate, partly because I want to
> check the system behaves correctly, and partly because I'm lazy.
>
> If any maintainer needs such a forward, let me know.
>
> -- 
> Bastien





  reply	other threads:[~2008-11-25  9:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23 23:53 org changes lost Glenn Morris
2008-11-24  2:36 ` Glenn Morris
2008-11-24  3:56   ` Miles Bader
2008-11-24 12:31     ` Carsten Dominik
2008-11-24 16:32       ` Chong Yidong
2008-11-25  9:30         ` Carsten Dominik
2008-11-24 17:29       ` Glenn Morris
2008-11-24 19:31         ` Bastien
2008-11-24 18:23       ` Reiner Steib
2008-11-25  9:24         ` Bastien
2008-11-25 17:44           ` Reiner Steib
2008-11-25  9:31         ` Carsten Dominik
2008-11-25  2:50       ` Stefan Monnier
2008-11-25  3:10         ` Chong Yidong
2008-11-25 15:11           ` Stefan Monnier
2008-11-25  9:01         ` Yavor Doganov
2008-11-25 15:14           ` Stefan Monnier
2008-11-25  9:03         ` Bastien
2008-11-25  9:33           ` Carsten Dominik [this message]
2008-11-25 15:19           ` Stefan Monnier
2008-11-25 17:11             ` Bastien
2008-11-25  9:38         ` Carsten Dominik
2008-11-26  3:20           ` Michael Olson
2008-11-24 11:06 ` Carsten Dominik

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=0D52CA63-7E8D-474F-8DDA-F64278A85801@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=bastienguerry@googlemail.com \
    --cc=emacs-devel@gnu.org \
    --cc=lektu@terra.es \
    --cc=miles@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rgm@gnu.org \
    /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).