From: "Stephen Dawes" <sdawes@telus.net>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: location of the speakup users guide
Date: Mon, 6 Dec 2010 05:48:59 -0700 [thread overview]
Message-ID: <CAD9936731714748B79DD5BB97DF2C58@Puma> (raw)
In-Reply-To: <20101205235427.GA3367@linux1>
Shouldn't it reside in a speakupdocs branch of the speakup tree? I don't
think that code and documentation belong in the same branch. If this is not
acceptable, follow the kernel documentation structure.
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of William Hubbs
Sent: Sunday, December 05, 2010 4:54 PM
To: speakup mailing list
Subject: rfc: location of the speakup users guide
All,
I don't know for sure how I want to do this, so I want to run it by the rest
of you to see what you think.
Currently, we have the speakup users guide located in the staging directory,
which means that it shows up in the linux kernel source tree.
We can't put it in the Documentation directory of the kernel until it goes
fully mainline (out of staging).
So, I'm wondering what you think about where it is located now. Should it
be in the staging directory where it is, or, should we move it, e.g.
to the speakup-tools repository?
Comments?
Thanks,
William
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
rfc: " William Hubbs
` Littlefield, Tyler
` Zachary Kline
` Stephen Dawes [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAD9936731714748B79DD5BB97DF2C58@Puma \
--to=sdawes@telus.net \
--cc=speakup@braille.uwo.ca \
/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).