public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: William Hubbs <w.d.hubbs@gmail.com>
To: speakup mailing list <speakup@braille.uwo.ca>
Subject: preparing speakup for staging
Date: Thu, 7 Oct 2010 19:15:47 -0500	[thread overview]
Message-ID: <20101008001547.GB18994@linux1> (raw)

All,

I am currently going through the speakup code to start preparing it to
be submitted to the kernel developers  for the "staging" tree, which is
the first step for kernel inclusion.

One of those changes will make git speakup incompatible with kernels
before 2.6.31.

For the rest of the developers, the issue is that LINUX_VERSION_CODE is
not supposed to be used in the version of speakup we send upstream.

It was suggested to me that I should do that part of the sgaging work on
a separate branch in our repository.  But, I don't  think that is a good
idea, because it means that we would have to maintain two
branches in the repository from now on and make sure that all changes to
master went to the other branch as well.

If no one objects by 0  utc on Sunday, I will consider the master branch
fair game for pushing this change.

Thanks,

William


             reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 William Hubbs [this message]
 ` William Hubbs
 ` Samuel Thibault
   ` Steve Holmes
     ` William Hubbs

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=20101008001547.GB18994@linux1 \
    --to=w.d.hubbs@gmail.com \
    --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).