From: Carsten Dominik <carsten.dominik@gmail.com>
To: Erik Iverson <eriki@ccbr.umn.edu>
Cc: Emacs-orgmode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Development setup (was: Org-mode release 7.01)
Date: Tue, 20 Jul 2010 08:29:35 +0200 [thread overview]
Message-ID: <181367C6-0C79-439B-B798-FAA0BB6C02C3@gmail.com> (raw)
In-Reply-To: <4C450AB4.8010202@ccbr.umn.edu>
On Jul 20, 2010, at 4:32 AM, Erik Iverson wrote:
>
>>
>>
>> Suggestions:
>>
>> 1.) Could the original mail (the one including the actual patch,
>> even if
>> modified) be attached to the autogenerated email, please?
>> This should be at the very bottom of the mail, because of
>> length and
>> priority.
>>
>> 2.) And how about the subject? The OP's subject is what I read on
>> the
>> patchwork server. Why can't that be (part of) the subject of the
>> "Accepted" message? E.g.:
>>
>> [Orgmode] [ACCEPTED] org-capture with LISP function template
>>
>> Maybe something that works on gmane et al, too.
>>
>> 3.) If there are annotations to the patch, would it be possible to
>> include that comment in that automated message? I don't now
>> how the
>> patch is switched to accepted on the patchwork server. But a
>> simple
>> textarea field and appropriate POST variable would do, wouldn't
>> it?
>
> 4) If traffic warrants it and as more users join this list
> generating more posts... perhaps a new list called emacs-orgmode-dev
> for development related work?
This proposal has come up in the past, but so far the conclusion
always has been that we still prefer to keep things together.
I guess with modern email readers with filtering, high volumne
mailing lists do not present a big issue.
May people already prefix email subject with [PATCH] or "Bug:",
which helps in filtering.
- Carsten
next prev parent reply other threads:[~2010-07-20 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 0:01 Development setup (was: Org-mode release 7.01) Sebastian Rose
2010-07-20 2:32 ` Erik Iverson
2010-07-20 6:29 ` Carsten Dominik [this message]
2010-07-20 6:26 ` Carsten Dominik
2010-07-20 23:00 ` Sebastian Rose
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=181367C6-0C79-439B-B798-FAA0BB6C02C3@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eriki@ccbr.umn.edu \
/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/org-mode.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).