From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: File specific exporting of tags
Date: Tue, 20 Nov 2007 12:37:53 +0000 [thread overview]
Message-ID: <87zlx9drdq.fsf@bzg.ath.cx> (raw)
In-Reply-To: <52D89C75FEE9444E8D9C016E3730098306CE69@chsa1036.share.beluni.net> (Egli Christian's message of "Tue, 20 Nov 2007 11:31:03 +0100")
Hi Christian and all,
I'd just like to add a bit of clarification on two points.
"Egli Christian (KIRO 41)" <christian.egli@credit-suisse.com> writes:
> I appreciate the time you took to analyse the problem and propose a
> solution. I was just hinting that producing a patch to the documentation
> is very easy (in fact that is how I got into hacking on org-mode :-))
Sure, and if anyone *likes* this way of proposing a change, let's go for
it! But unless one is 95% sure that the patch is accurate (e.g. when it
is a change on typos), I guess it will be enough to send a suggestion --
especially if using diff is more work than anything...
> and will IMHO give the developers more time to focus on the code. The
> documentation in org.texi is basically text with some markup and can be
> adapted easily, so no lisp know-how required.
It's been several times that the word "developpers" appeared in its
plural form... While I would happily put myself into that category, I
think people should bare in mind that I'm only providing patches and
suggestions -- and Carsten _is_ the developper !
Having successfully hijacked a mailing list should not be a reason to be
held as a "developper".
:)
--
Bastien
prev parent reply other threads:[~2007-11-20 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 1:38 File specific exporting of tags Daniel J. Sinder
2007-11-19 2:51 ` Bastien
2007-11-19 8:19 ` Egli Christian (KIRO 41)
2007-11-19 20:10 ` Daniel J. Sinder
2007-11-20 0:23 ` Bastien
2007-11-20 10:31 ` Egli Christian (KIRO 41)
2007-11-20 12:37 ` Bastien [this message]
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=87zlx9drdq.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--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).