From: Giovanni Ridolfi <giovanni.ridolfi@yahoo.it>
To: nicholas.dokos@hp.com
Cc: Bernt Hansen <bernt@norang.ca>,
emacs-orgmode@gnu.org,
Roland Kaufmann <rlndkfmn+orgmode@gmail.com>
Subject: Re: Markup problems when using references in source fragments
Date: Thu, 12 May 2011 12:56:36 +0200 [thread overview]
Message-ID: <83ei446vbv.fsf@yahoo.it> (raw)
In-Reply-To: <5257.1305183584@alphaville.dokosmarshall.org> (Nick Dokos's message of "Thu, 12 May 2011 02:59:44 -0400")
Nick Dokos <nicholas.dokos@hp.com> writes:
> Bernt Hansen <bernt@norang.ca> wrote:
>
>> Roland Kaufmann <rlndkfmn+orgmode@gmail.com> writes:
>>
>> > . The patch which is listed there should *not* be
>> > applied.
>> I think you can create an account on the patchwork server and then
>> invalidate your own patches.
>>
>
> If this is possible, can somebody please give details?
>
> And while we are at it: is there any way to mark a post that contains a
> patch as "not intended for the patchwork server"?
If you think that a patch is
"not intended for the patchwork server"
you may write an e-mail to the patchwork maintainers:
John Wiegley <johnw@newartisans.com>
Carsten Dominik <carsten.dominik@gmail.com>
Eric Schulte <schulte.eric@gmail.com>
Bastien Guerry <bzg@altern.org>
Dan Davison <dandavison7@gmail.com>
David Maus <dmaus@ictsoc.de>
Julien Danjou <julien@danjou.info>
with the subject: REMOVE patches
and link the number of the patches to be removed.
I think they can do that easily from the command line.
I have done this way 3 or 4 times in the past.
I also added some comments/justification: e.g. the link of the
e-mail pointing out that it is a wrong patch or incomplete or...
HTH
Giovanni
next prev parent reply other threads:[~2011-05-12 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 19:41 Markup problems when using references in source fragments (was: Markup on same line as text) Roland Kaufmann
2011-05-11 19:51 ` Markup problems when using references in source fragments Bernt Hansen
2011-05-11 20:06 ` Roland Kaufmann
2011-05-11 20:21 ` Bernt Hansen
2011-05-12 6:59 ` Nick Dokos
2011-05-12 10:56 ` Giovanni Ridolfi [this message]
2011-05-12 12:43 ` Bernt Hansen
2011-05-12 13:48 ` Nick Dokos
2011-05-25 7:41 ` Markup problems when using references in source fragments (was: Markup on same line as text) Carsten Dominik
2011-05-25 10:31 ` 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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ei446vbv.fsf@yahoo.it \
--to=giovanni.ridolfi@yahoo.it \
--cc=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
--cc=rlndkfmn+orgmode@gmail.com \
/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).