unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bastien <bastienguerry@googlemail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Miles Bader <miles@gnu.org>, Glenn Morris <rgm@gnu.org>,
	Emacs developers <emacs-devel@gnu.org>,
	Juanma Barranquero <lektu@terra.es>,
	Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: org changes lost
Date: Tue, 25 Nov 2008 18:11:19 +0100	[thread overview]
Message-ID: <871vwzu3wo.fsf@gnu.org> (raw)
In-Reply-To: <jwvprkjn8h1.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 25 Nov 2008 10:19:53 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> IIUC emacs-diffs should now be a superset of emacs-commit, so
> emacs-commit should not be necessary.

Okay, I'm just forwarding emacs-diffs.

>> I've not done this for all Emacs projects so far, partly because the
>> MAINTAINERS file might not be 100% accurate,
>
> It's OK if it's not accurate: that will hopefully prompt people to make
> it more accurate.  But the main source of such info is in the header of
> each Elisp file (look for ";; Author:" or ";; Maintainer: " in the
> section between the first line and the ";;; Commentary").  Look at
> lisp-mnt.el for some utility functions that can find that field for you.

I understand the setup you have in mind, but I don't I don't feel
comfortable in automatically forwarding emails to people I don't know.

I suggest we first send an email to all the maintainers asking them if
they want such a reminder for themselves.  Maybe most of them already
filter through [emacs-diffs] and don't need additional forwards.  And
maybe encouraging *every* Emacs developer to only stay focused on his
own piece of code will is not a good thing to do.

Thoughts?

-- 
 Bastien




  reply	other threads:[~2008-11-25 17:11 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
2008-11-25 15:19           ` Stefan Monnier
2008-11-25 17:11             ` Bastien [this message]
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=871vwzu3wo.fsf@gnu.org \
    --to=bastienguerry@googlemail.com \
    --cc=carsten.dominik@gmail.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).