From: Bastien <bastienguerry@googlemail.com>
To: Christian Egli <christian.egli@sbszh.ch>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: suggestion: converting plain lists to subtrees
Date: Sat, 25 Jul 2009 19:57:07 +0800 [thread overview]
Message-ID: <87ab2tasbw.fsf@bzg.ath.cx> (raw)
In-Reply-To: <j2ljmev76x.fsf@saadawi.sbszh.ch> (Christian Egli's message of "Fri, 24 Jul 2009 10:03:34 +0200")
Christian Egli <christian.egli@sbszh.ch> writes:
> I'm not such a big fan of code or documentation duplication. Here's a
> patch that removes this duplication and simply refers to the original
> section on C-c *.
Well spotted, thanks, I applied the patch.
--
Bastien
next prev parent reply other threads:[~2009-07-25 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 17:21 suggestion: converting plain lists to subtrees Ilya Shlyakhter
2009-07-21 18:09 ` Dan Davison
2009-07-21 20:23 ` Bastien
2009-07-24 8:03 ` Christian Egli
2009-07-25 11:57 ` Bastien [this message]
2009-07-25 22:12 ` Bastien
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=87ab2tasbw.fsf@bzg.ath.cx \
--to=bastienguerry@googlemail.com \
--cc=christian.egli@sbszh.ch \
--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).