From: Tyler Smith <tyler.smith@mail.mcgill.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: managing multiple dir files
Date: 15 Mar 2008 11:37:54 GMT [thread overview]
Message-ID: <slrnftnd8h.te.tyler.smith@blackbart.sedgenet> (raw)
In-Reply-To: mailman.8844.1205419949.18990.help-gnu-emacs@gnu.org
On 2008-03-13, Peter Dyballa <Peter_Dyballa@Web.DE> wrote some handy
tips for managing my info tree:
Thanks Pete! I've gone through my dir files and reorganized them to my
liking. I'll keep an eye on them now, and find out which packages get
double-listed. Then I'll try digging into them and modifying the build
instructions, or submitting bug reports if appropriate.
Cheers,
Tyler
prev parent reply other threads:[~2008-03-15 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 16:42 managing multiple dir files Tyler Smith
2008-03-13 9:00 ` Peter Dyballa
[not found] ` <mailman.8826.1205398841.18990.help-gnu-emacs@gnu.org>
2008-03-13 12:24 ` Tyler Smith
2008-03-13 14:52 ` Peter Dyballa
2008-03-13 17:33 ` Peter Dyballa
[not found] ` <mailman.8844.1205419949.18990.help-gnu-emacs@gnu.org>
2008-03-15 11:37 ` Tyler Smith [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.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=slrnftnd8h.te.tyler.smith@blackbart.sedgenet \
--to=tyler.smith@mail.mcgill.ca \
--cc=help-gnu-emacs@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.
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).