From: Arun Isaac <arunisaac@systemreboot.net>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 27673@debbugs.gnu.org
Subject: [bug#27673] [PATCH] gnu: Add emacs-org-pomodoro.
Date: Fri, 14 Jul 2017 17:25:29 +0530 [thread overview]
Message-ID: <2beb7d1c.AEQANFFEJwcAAAAAAAAAAAPVUpsAAAACwQwAAAAAAAW9WABZaLFC@mailjet.com> (raw)
In-Reply-To: <20170712204731.14463-1-go.wigust@gmail.com>
Thanks for the patch!
> +(define-public emacs-org-pomodoro
> + (package
> + (name "emacs-org-pomodoro")
> + (version "2.1.0")
> + (source (origin
> + (method url-fetch)
> + (uri (string-append
> + "https://github.com/lolownia/org-pomodoro/archive/"
> + version ".tar.gz"))
> + (file-name (string-append name "-" version ".tar.gz"))
> + (sha256
> + (base32
> + "1jalsggw3q5kvj353f84x4nl04a5vmq07h75ggppy1627lb31zm4"))))
> + (build-system emacs-build-system)
Could you also package the tests? You'll need something very similar to
what the emacs-which-key package has.
> + (propagated-inputs
> + `(("emacs-alert" ,emacs-alert)))
> + (home-page "https://github.com/lolownia/org-pomodoro")
> + (synopsis "Pomodoro technique for org-mode")
> + (description
> + "@code{emacs-org-pomodoro} adds very basic support for Pomodoro technique
> +in Emacs org-mode.")
Could you extend the description a little more, perhaps by paraphrasing
paragraph 3 of README.md...?
next prev parent reply other threads:[~2017-07-14 11:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 20:47 [bug#27673] [PATCH] gnu: Add emacs-org-pomodoro Oleg Pykhalov
2017-07-14 11:55 ` Arun Isaac [this message]
[not found] ` <52c335a3.AEQANFFEJwgAAAAAAAAAAAPNhpIAAAACwQwAAAAAAAW9WABZaLFC@mailjet.com>
2017-07-14 13:49 ` [bug#27673] Failing tests Oleg Pykhalov
2017-07-14 14:11 ` Arun Isaac
2017-07-14 15:12 ` Leo Famulari
2017-07-14 16:34 ` Oleg Pykhalov
2017-07-17 9:46 ` bug#27673: " Arun Isaac
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=2beb7d1c.AEQANFFEJwcAAAAAAAAAAAPVUpsAAAACwQwAAAAAAAW9WABZaLFC@mailjet.com \
--to=arunisaac@systemreboot.net \
--cc=27673@debbugs.gnu.org \
--cc=go.wigust@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/guix.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.