From: John Williams <john.williams@otago.ac.nz>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: eww
Date: Thu, 01 Aug 2013 22:59:32 +1100 [thread overview]
Message-ID: <87ehad4o63.fsf@otago.ac.nz> (raw)
In-Reply-To: <m31u82jed6.fsf@stories.gnus.org>
I would like to help test eww, but I am not a Lisp programmer (although
I have hobby-level development experience with other programming
languages). I can see here:
http://git.gnus.org/cgit/gnus.git/tree/lisp?id=d54fa592ab919f897f6d0505b70beb90153e561f
that eww.el is in some git branch, but when I follow the instructions
here:
http://git.gnus.org/cgit/gnus.git/about/
and say:
"git clone http://git.gnus.org/gnus.git && cd gnus && git checkout m0-7"
I cannot see this file. Could someone help me check out a
revision/branch/whatever that includes eew please? And also, tell me
how a non-coder (or "a little knowledge is a dangerous thing" coder)
could help with the development of this very, very exciting project?
Thanks heaps,
John
next prev parent reply other threads:[~2013-08-01 11:59 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 14:53 eww Lars Magne Ingebrigtsen
2013-06-16 15:21 ` eww Adam Sjøgren
2013-06-16 15:29 ` eww Lars Magne Ingebrigtsen
2013-06-16 15:46 ` eww Lars Magne Ingebrigtsen
2013-06-16 17:01 ` eww Dmitry Gutov
2013-06-16 17:06 ` eww Lars Magne Ingebrigtsen
2013-06-17 21:00 ` eww Lars Magne Ingebrigtsen
2013-06-17 23:35 ` eww Ted Zlatanov
2013-06-18 0:01 ` eww Lars Magne Ingebrigtsen
2013-07-09 13:20 ` eww Ted Zlatanov
2013-08-01 14:39 ` eww Lars Magne Ingebrigtsen
2013-07-09 10:23 ` eww Julien Cubizolles
2013-07-09 10:42 ` eww David Edmondson
2013-06-16 23:42 ` eww lee
2013-06-17 5:57 ` eww Lars Magne Ingebrigtsen
2013-06-17 18:46 ` eww lee
2013-06-18 2:19 ` eww Tom Tromey
2013-06-18 11:23 ` eww Lars Magne Ingebrigtsen
2013-06-18 14:34 ` eww Tom Tromey
2013-06-18 15:01 ` eww Lars Magne Ingebrigtsen
2013-06-18 15:43 ` eww Tom Tromey
2013-06-18 14:39 ` eww Tom Tromey
2013-06-18 15:14 ` eww Lars Magne Ingebrigtsen
2013-06-18 16:17 ` eww Tom Tromey
2013-06-18 19:06 ` eww Steinar Bang
2013-06-18 19:07 ` eww Stefan Monnier
2013-06-18 11:31 ` eww Lars Magne Ingebrigtsen
2013-06-18 14:42 ` eww Tom Tromey
2013-06-18 15:04 ` eww Lars Magne Ingebrigtsen
2013-06-18 19:13 ` eww Stefan Monnier
2013-06-18 19:17 ` eww Eli Zaretskii
2013-06-18 20:21 ` eww Stefan Monnier
2013-06-18 23:34 ` eww James Cloos
2013-06-19 2:50 ` eww Eli Zaretskii
2013-06-19 4:49 ` eww Stefan Monnier
2013-06-18 23:03 ` eww Xue Fuqiao
2013-06-19 3:03 ` eww Eli Zaretskii
2013-06-18 19:27 ` eww Tom Tromey
2013-06-18 23:40 ` eww Juri Linkov
2013-06-19 0:51 ` eww Stefan Monnier
2013-06-19 1:08 ` eww Russ Allbery
2013-06-19 10:14 ` eww Rasmus
2013-06-19 10:34 ` eww Christopher Schmidt
2013-06-25 7:43 ` eww lee
2013-06-25 9:05 ` eww Tassilo Horn
2013-06-25 13:27 ` eww Steinar Bang
2013-06-27 9:05 ` eww lee
2013-06-18 11:32 ` eww joakim
2013-06-18 12:16 ` eww Andreas Schwab
2013-06-18 13:57 ` eww Lars Magne Ingebrigtsen
2013-06-18 14:01 ` eww joakim
2013-06-19 10:21 ` eww Ivan Kanis
2013-06-19 11:52 ` eww Steinar Bang
2013-06-19 12:14 ` eww Ivan Kanis
2013-08-01 11:59 ` John Williams [this message]
2013-08-02 0:20 ` eww John Williams
2013-08-02 0:27 ` eww Lars Magne Ingebrigtsen
2013-08-02 19:48 ` eww Richard Stallman
2013-08-03 11:30 ` eww Lars Magne Ingebrigtsen
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=87ehad4o63.fsf@otago.ac.nz \
--to=john.williams@otago.ac.nz \
--cc=ding@gnus.org \
--cc=emacs-devel@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.
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 NNTP newsgroup(s).