From: Tim Landscheidt <tim@tim-landscheidt.de>
To: emacs-orgmode@gnu.org
Cc: John Wiegley <jwiegley@gmail.com>
Subject: Purpose of mk/pw?
Date: Wed, 17 Jan 2018 11:23:43 +0000 [thread overview]
Message-ID: <87h8rkg24g.fsf@passepartout.tim-landscheidt.de> (raw)
Hi,
mk/pw seems to have not been touched in a long time, and
whatever it did, it does not seem to do it nowaways:
| [tim@passepartout ~/src/org-mode]$ mk/pw list
| Traceback (most recent call last):
| File "mk/pw", line 664, in <module>
| main()
| File "mk/pw", line 585, in main
| action_list(rpc, filt, submitter_str, delegate_str)
| File "mk/pw", line 190, in action_list
| filter.resolve_ids(rpc)
| File "mk/pw", line 76, in resolve_ids
| id = state_id_by_name(rpc, self.state)
| File "mk/pw", line 168, in state_id_by_name
| states = rpc.state_list(name, 0)
| File "/usr/lib64/python2.7/xmlrpclib.py", line 1243, in __call__
| return self.__send(self.__name, args)
| File "/usr/lib64/python2.7/xmlrpclib.py", line 1602, in __request
| verbose=self.__verbose
| File "/usr/lib64/python2.7/xmlrpclib.py", line 1283, in request
| return self.single_request(host, handler, request_body, verbose)
| File "/usr/lib64/python2.7/xmlrpclib.py", line 1331, in single_request
| response.msg,
| xmlrpclib.ProtocolError: <ProtocolError for patchwork.newartisans.com/xmlrpc/: 404 Not Found>
| [tim@passepartout ~/src/org-mode]$
(http://patchwork.newartisans.com/ itself is 404 as well.)
Is it still relevant? If it was some kind of patch queue,
is that aspect now sufficiently handled by
https://code.orgmode.org/bzg/org-mode/pulls?
Tim
next reply other threads:[~2018-01-17 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 11:23 Tim Landscheidt [this message]
2018-01-17 19:52 ` Purpose of mk/pw? Nicolas Goaziou
2018-02-05 14:18 ` Tim Landscheidt
2018-02-05 14:40 ` Nicolas Goaziou
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8rkg24g.fsf@passepartout.tim-landscheidt.de \
--to=tim@tim-landscheidt.de \
--cc=emacs-orgmode@gnu.org \
--cc=jwiegley@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.