From: Julien Danjou <julien@danjou.info>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Bernt Hansen <bernt@norang.ca>, emacs-orgmode@gnu.org
Subject: Re: Re: [PATCH] org: rework property set
Date: Thu, 16 Dec 2010 14:45:00 +0100 [thread overview]
Message-ID: <sa31v5h6dcz.fsf@cigue.easter-eggs.fr> (raw)
In-Reply-To: <15A20FD1-21EA-418E-A585-D9D56BF0FF3F@gmail.com> (Carsten Dominik's message of "Thu, 16 Dec 2010 14:34:06 +0100")
[-- Attachment #1.1: Type: text/plain, Size: 367 bytes --]
On Thu, Dec 16 2010, Carsten Dominik wrote:
> are you going to resend the patch? I do like the functionality!
> Or did you already resend it? Maybe I missed it. Unfortunately
> I am loosing my overview here.
If the code seems fine to you, I can resend the patch with a clean
commit message, for sure.
--
Julien Danjou
❱ http://julien.danjou.info
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-12-16 13:45 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 17:29 [PATCH] org: rework property set Julien Danjou
2010-12-13 21:21 ` Bernt Hansen
2010-12-14 9:01 ` Julien Danjou
2010-12-14 10:15 ` Giovanni Ridolfi
2010-12-14 10:30 ` Julien Danjou
2010-12-14 12:28 ` Bernt Hansen
2010-12-16 13:34 ` Carsten Dominik
2010-12-16 13:45 ` Julien Danjou [this message]
2010-12-16 13:55 ` Carsten Dominik
2010-12-16 17:12 ` Julien Danjou
2010-12-17 17:39 ` Carsten Dominik
[not found] ` <julien@danjou.info>
2010-12-14 14:50 ` Nick Dokos
2011-03-17 17:27 ` Re: Problem with agenda and diary Nick Dokos
2011-03-17 18:18 ` Tassilo Horn
2011-03-17 19:06 ` Dan Griswold
2011-03-17 19:45 ` Nick Dokos
2011-03-17 20:37 ` Dan Griswold
2011-03-17 22:01 ` Nick Dokos
2011-03-17 22:11 ` Nick Dokos
2011-03-18 10:36 ` Julien Danjou
2011-03-18 10:36 ` Julien Danjou
2011-03-18 14:04 ` Nick Dokos
2011-03-18 14:14 ` Nick Dokos
2011-03-18 14:56 ` Bernt Hansen
2011-03-18 15:20 ` Bastien
2011-03-18 15:33 ` Nick Dokos
2011-03-18 16:27 ` Julien Danjou
2011-03-19 10:20 ` Bastien
2011-03-19 10:20 ` Bastien
2011-03-18 14:22 ` Julien Danjou
2011-03-18 14:51 ` Julien Danjou, Nick Dokos
2011-03-18 15:05 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2011-03-17 13:30 Dan Griswold
2011-03-17 13:39 ` Erik Iverson
2011-03-17 13:48 ` Tassilo Horn
2011-03-17 14:45 ` Julien Danjou
2011-03-17 15:34 ` Tassilo Horn
2011-03-17 16:46 ` Julien Danjou
2011-03-17 20:28 ` Sébastien Vauban
2011-03-17 22:06 ` Nick Dokos
2011-03-17 23:43 ` Sébastien Vauban
2011-03-18 0:20 ` Nick Dokos
2011-03-18 10:07 ` Bastien
2011-03-17 14:48 ` Dan Griswold
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=sa31v5h6dcz.fsf@cigue.easter-eggs.fr \
--to=julien@danjou.info \
--cc=bernt@norang.ca \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).