tests: Provide a unit test for clean_subject()

The intended behaviour is documented in the doc string of that function,
we might as well add the corresponding unit test!

Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
tests: Fix a typo in the MboxPassThroughHeaderTest description

Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
docs: Update the database configuration instructions

That's the "new" (django 1.5+) way of defining databases, strictly
following the instructions wasn't working. This should save the next
user a bit of time.

Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
doc: Sprinkle a few UTF-8 in the mysql documentation

When not specifying the charset/collation, I managed to create a latin1
database where all strings were encoded in latin1. That's really not
ideal. Adding 'CHARACTER SET utf8' when creating the DB fixes it. Then:

$ ./manage.py syncdb

will correctly create tables with UTF-8 encoded rows.

However, for some reason, when django creates the test tables, that
default, DB wide, encoding is not respected and one needs to provide an
additional TEST_CHARSET entry in the config dictionary.

Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
parsemail: Return the list of prefixes when cleaning up the subject

The patch is a preparation step towards understanding series. It will be
handy to parse those prefixes, looking for 'x/n' to retrieve the order
of a patch in a series.

Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
parsemail: Make find_content() return a MailContent object

Returning tuples is not super scalable. I now want to return a Series
object along with a patch or a comment. So let's put the return values
into a class, used as a typed dictionary really.

Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
parsemail: Add a function to parse series markers eg. "1/12"

This can be used to identify cover letters, patches part of series,
length of series, ...

Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
parsemail: Extract building the list of mail references

We'll need to figure out whether the mail we are parsing is the root of
the thread to automatically build series, and we'll need the list of
references for that.

Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
parsemail: Strip mail signatures from comments

Those signature don't really add value to the comment.

Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
tests: Make sure all emails have a valid msgid

Messages ids will be used by the Series code as the way to uniquely
identify series. We must ensure every single email that goes through the
parser has a valid msgid to not fail once we parse series.

Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
gitignore: Only ignore quilt files at the root of the repositories

So say, a series directory in the project (added in a later patch) is
not ignored.

Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
series: Add the concept of series

Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
added foreign key seriesid to class patch
added the new architecture to series and patch
Changed the add_patch to add_series and added the seriesid to class patch with add_series function. Signed off by: Michelle Nieman
Added seriesid to class patch and added function add_series. Signed-off-by: Michelle Nieman
Added seriesid to class patch and added function add_series. Signed-off-by: Michelle Nieman
Added seriesid to class patch and added function add_series. Signed-off-by: Michelle Nieman