From: Kazuo Teramoto <kaz.rag@gmail.com>
To: Justus Winter <4winter@informatik.uni-hamburg.de>,
notmuch@notmuchmail.org
Subject: Re: [afew] announcing afew,
Date: Wed, 14 Dec 2011 09:24:14 -0200 [thread overview]
Message-ID: <4ee88760.68b8ec0a.5641.ffff942f@mx.google.com> (raw)
In-Reply-To: <E1RamIG-0003si-K3@thinkbox.jade-hamburg.de>
an universal tagging solution with some fancy features
From: Kazuo Teramoto <kaz.rag@gmail.com>
In-Reply-To: <E1RamIG-0003si-K3@thinkbox.jade-hamburg.de>
On 2011-12-14T08:42:36, Justus Winter wrote:
>I'd like to introduce my initial tagging approach, afew tags:
>
>https://github.com/teythoon/afew
>
Very good! Thanks for it. I'm using it as my only filtering/tagging
solutions and works great.
I created a Arch Linux PKGBUILD, it can be find at [aur] (about it,
Justus how you define the afew license? I put a 'unknown' in the license
as I can give it a names like BSD or GPL or WTFPL).
>* works with both python2.7 and python3.2
>
Python 3 support need the patch set you send to the list, correct?
Regards,
Kazuo
[aur]: https://aur.archlinux.org/packages.php?ID=54532
next prev parent reply other threads:[~2011-12-14 11:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 10:42 [afew] announcing afew, an universal tagging solution with some fancy features Justus Winter
2011-12-14 11:24 ` Kazuo Teramoto [this message]
2011-12-14 12:10 ` [afew] announcing afew, Justus Winter
2011-12-14 13:07 ` [afew] announcing afew, an universal tagging solution with some fancy features Jani Nikula
2011-12-14 16:59 ` Patrick Totzke
2011-12-19 14:13 ` Justus Winter
2011-12-19 17:57 ` Jameson Graef Rollins
2011-12-19 18:17 ` Patrick Totzke
2011-12-21 8:53 ` Justus Winter
2012-01-20 10:40 ` Patrick Totzke
2012-01-20 11:26 ` Justus Winter
2012-01-20 21:55 ` Kazuo Teramoto
2012-01-21 0:13 ` Justus Winter
2011-12-21 8:38 ` Justus Winter
2012-02-27 21:10 ` James Vasile
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ee88760.68b8ec0a.5641.ffff942f@mx.google.com \
--to=kaz.rag@gmail.com \
--cc=4winter@informatik.uni-hamburg.de \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.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).