emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Sebastian Rose <sebastian_rose@gmx.de>
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:26:18 +0200	[thread overview]
Message-ID: <4C058B7B-F6E9-490B-9467-4A6B77B1EDAC@gmail.com> (raw)
In-Reply-To: <87zkxnja2h.fsf@gmx.de>

Hi Sebastian,

I would like to fix this as well but have not yet had the time to
do so and I am being hampered by my limited knowledge of python
and of the patchwork server.

This will change, but I don't know how fast.

- Carsten

On Jul 20, 2010, at 2:01 AM, Sebastian Rose wrote:

> Hi Carsten and John,
>
>
>> Also, I need to shout out my gratitude to the increasing number of
>> volunteers in the project.
>>
>> John Wiegley's patchwork server has done wonders for streamlining the
>> process of reviewing and applying patches.  I have applied dozens of
>> patches though this process, just in the last week.
>>
>> The issue tracker by David Maus has finally brought some structure
>> into the stream of ideas and reports on this mailing list, at a
>> moment when I was about to falter under the amount of work
>> maintaining this project means for me.  Frankly,  right now I
>> don't know how I would do things without David's competent and
>> efficient help - he has effectively and silently become
>> co-maintainer of this project.
>
>
> The new technique drives me crazy.  To me, it feels frustrating  
> compared
> to the direct means of "the good old times".
>
>
> Now, that the release is done, it's time to speak about the next  
> decade
> of Org mode developing ;)
>
>
>
> A minute ago I got 5 mails like this one here:
>
>
> Subject:
>
>     "Patchwork: Patch 150 Accepted"
>
> Body:
>
>    Patch 145 (http://patchwork.newartisans.com/patch/145/) is now  
> Accepted.
>
>    This relates to the following submission:
>
>    http://mid.gmane.org/%3C1279347713-29950-1-git-send-email-dmaus%40ictsoc.de%3E
>
>
>
>
> This current mechanism might help the maintainers as it's automated,  
> but
> for me it's hard to follow.
>
> I often delete mails suggesting patches I don't apprehend.  I then get
> those dangling "Patchwork: ..." messages.  I simply don't want to  
> gather
> all those mails from this high traffic list, just to now to which
> issue the accepted patches belong.
>
> I don't want to click the link(s) in those mails and wait for my  
> browser
> to load either.
>
>
> 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?
>
>
>
> This is all information available on the patchwork server.  So I hope
> it's just changing a few lines of code?
>
> I sometimes receive mails from bugzilla servers, concerning bug  
> reports
> I wrote years ago.  I never had that problem to understand what those
> mails were trying to tell me.
>
>
> Thanks for considering this.
>
>
> Best wishes
>
>  Sebastian
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

- Carsten

  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
2010-07-20  6:26 ` Carsten Dominik [this message]
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=4C058B7B-F6E9-490B-9467-4A6B77B1EDAC@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sebastian_rose@gmx.de \
    /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).