From: Bernt Hansen <email@example.com>
To: John Hendy <firstname.lastname@example.org>
Cc: Bastien <email@example.com>, emacs-orgmode <firstname.lastname@example.org>
Subject: Re: [Orgmode] Grouping clock report by tag?
Date: Fri, 06 May 2011 19:55:22 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <BANLkTi=-de-wwrPVEe6ZaThVoC0Fvtgp7Q@mail.gmail.com> (John Hendy's message of "Fri, 6 May 2011 15:30:12 -0500")
John Hendy <firstname.lastname@example.org> writes:
> On Thu, May 5, 2011 at 6:08 PM, Bernt Hansen <email@example.com> wrote:
>> Niels Giesen posted some patches for summarizing clock reports by
>> arbitrary properties. Maybe this will be useful?
>> I'm not aware of any functionality that does what you describe above.
> His is actually pretty darn close. It looks like Carsten just
> re-requested a patch in some standard format a few days ago, so
> perhaps I can hold my breath for it to get applied. Otherwise, do I
> just copy/paste his code into manual files and then do something like
> 'patch -p0 file.patch'?
> And will it get overrun by my next pull?
> Sorry... never applied a patch to org-mode files.
Creating the patches is fairly easy.
1) Take the email with the patches in it and cut out the #+begin_src
and #+end_src lines and everything in front of the first patch so
the file is just the 3 patches consecutively.
2) Save the file (I put mine in /tmp/patch)
3) Create a local topic branch for these patches
$ git checkout -b clock-report-by-property origin/master
4) Apply the patches to create the 3 commits on this branch
$ git am /tmp/patch
Then try it out.
I've done the above steps and pushed the result to
after fixing up the email address since git doesn't like the <at>
syntax provided in the mail.
I have not fixed the changelog entries for these patches but they
should be fine for just giving it a trial run.
You can grab the patches from my git repository with
$ git fetch git://git.norang.ca/org-mode.git ng/clock-reports-by-property
This will create a temporary ref called FETCH_HEAD which you can check
$ git checkout FETCH_HEAD
and later just go back to your master with
$ git checkout master
prev parent reply other threads:[~2011-05-06 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 0:25 Grouping clock report by tag? John Hendy
2011-03-06 13:20 ` Bastien
2011-03-06 17:02 ` John Hendy
2011-03-06 17:42 ` Bastien
[not found] ` <AANLkTim6kxpDVxXw5krSbpDK+x3=wfB2iqN6g9nWujx2@mail.gmail.com>
2011-03-06 18:08 ` John Hendy
2011-03-07 10:11 ` Giovanni Ridolfi
2011-03-11 22:06 ` John Hendy
2011-05-05 19:33 ` [Orgmode] " John Hendy
2011-05-05 23:08 ` Bernt Hansen
2011-05-06 20:30 ` John Hendy
2011-05-06 23:55 ` Bernt Hansen [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).