From: John Wiegley <johnw@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Eli Zaretskii <eliz@gnu.org>, John Task <q01@disroot.org>,
emacs-devel@gnu.org
Subject: Re: Extending timeclock.el
Date: Sat, 6 May 2023 12:23:04 -0700 [thread overview]
Message-ID: <7E224F6B-2670-4F6E-A245-499D4E28C51C@gnu.org> (raw)
In-Reply-To: <87sfc9xo2m.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
Just a quick clarification: Ledger is not a part of the GNU project, it’s a endeavor I started under the BSD (or MIT?) license that is currently being maintained by several people.
But that’s neither here nor there. Weather timeclock.el should be the junction point for going to and from other timelog formats is another question. It’s really a _very_ basic format: in, out, with optional “project closing out”.
John
> On May 6, 2023, at 12:22 PM, Ihor Radchenko <yantar92@posteo.net> wrote:
>
> It is not, AFAIU. As John Wiegley pointed, it is already used by GNU
> ledger.
[-- Attachment #2: Type: text/html, Size: 2359 bytes --]
next prev parent reply other threads:[~2023-05-06 19:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 19:15 Extending timeclock.el John Task
2023-05-06 6:09 ` Philip Kaludercic
2023-05-06 7:19 ` Eli Zaretskii
2023-05-06 18:35 ` John Wiegley
2023-05-06 18:48 ` Ihor Radchenko
2023-05-06 18:48 ` John Wiegley
2023-05-06 19:02 ` Ihor Radchenko
2023-05-06 19:00 ` John Wiegley
2023-05-06 19:09 ` Eli Zaretskii
2023-05-06 19:22 ` Ihor Radchenko
2023-05-06 19:23 ` John Wiegley [this message]
2023-05-06 22:10 ` Mike Kupfer
2023-05-09 16:44 ` Mike Kupfer
-- strict thread matches above, loose matches on Subject: below --
2023-05-06 15:47 John Task
2023-05-06 16:53 ` Eli Zaretskii
2023-05-06 16:46 John Task
2023-05-06 18:35 John Task
2023-05-06 19:21 John Task
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7E224F6B-2670-4F6E-A245-499D4E28C51C@gnu.org \
--to=johnw@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=q01@disroot.org \
--cc=yantar92@posteo.net \
/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.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).