launchpad-reviewers team mailing list archive

[Guruprasad <mp+437886@xxxxxxxxxxxxxxxxxx>]

Guruprasad has proposed merging ~lgp171188/launchpad:fix-typo-bugs-doctest into launchpad:master.

Commit message:
Fix a typo fixed in a doctest in sampledata as well

Also add 'distroname' to .codespell-ignore

Requested reviews:
  Launchpad code reviewers (launchpad-reviewers)

For more details, see:
https://code.launchpad.net/~lgp171188/launchpad/+git/launchpad/+merge/437886
-- 
Your team Launchpad code reviewers is requested to review the proposed merge of ~lgp171188/launchpad:fix-typo-bugs-doctest into launchpad:master.

diff --git a/.codespell-ignore b/.codespell-ignore
index 770e5aa..f84b1f6 100644
--- a/.codespell-ignore
+++ b/.codespell-ignore
@@ -1,3 +1,4 @@
 buildd
 changee
+distroname
 iterm
diff --git a/database/sampledata/current-dev.sql b/database/sampledata/current-dev.sql
index 2f4ef1b..e4d13cd 100644
--- a/database/sampledata/current-dev.sql
+++ b/database/sampledata/current-dev.sql
@@ -4937,7 +4937,7 @@ Not crashed.', NULL, NULL);
 INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (4, 1, 1, 'Problem exists between chair and keyboard', NULL, NULL);
 INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (5, 3, 1, 'We''ve seen something very similar on AIX with Gnome 2.6 when it is compiled with XFT support. It might be that the anti-aliasing is causing loopback devices to degrade, resulting in a loss of transparency at the system cache level and decoherence in the undelete function. This is only known to be a problem when the moon is gibbous.', NULL, NULL);
 INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (6, 4, 1, 'Sorry, it was SCO unix which appears to have the same bug. For a brief moment I was confused there, since so much code is known to have been copied from SCO into AIX.', NULL, NULL);
-INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (7, 5, 1, 'This would be a real killer feature. If there is already code to make it possible, why aren''t there tons of press announcements about the secuirty possibilities. Imagine - no more embarrassing emails for Mr Gates... everything they delete would actually disappear! I''m sure Redmond will switch over as soon as they hear about this. It''s not a bug, it''s a feature!', NULL, NULL);
+INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (7, 5, 1, 'This would be a real killer feature. If there is already code to make it possible, why aren''t there tons of press announcements about the security possibilities. Imagine - no more embarrassing emails for Mr Gates... everything they delete would actually disappear! I''m sure Redmond will switch over as soon as they hear about this. It''s not a bug, it''s a feature!', NULL, NULL);
 INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (8, 6, 1, 'Oddly enough the bug system seems only capable of displaying the first two comments that are made against a bug. I wonder why that is? Lets have a few more decent legth comments in here so we can see what the spacing is like. Also, at some stage, we''ll need a few comments that get displayed in a fixed-width font, so we have a clue about code-in-bug-comments etc.', NULL, NULL);
 INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (9, 10, 1, 'Initial bug report.', NULL, NULL);
 INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (10, 11, 1, 'A test description', NULL, NULL);
diff --git a/database/sampledata/current.sql b/database/sampledata/current.sql
index ff2880d..37d089b 100644
--- a/database/sampledata/current.sql
+++ b/database/sampledata/current.sql
@@ -4851,7 +4851,7 @@ Not crashed.', NULL, NULL);
 INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (4, 1, 1, 'Problem exists between chair and keyboard', NULL, NULL);
 INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (5, 3, 1, 'We''ve seen something very similar on AIX with Gnome 2.6 when it is compiled with XFT support. It might be that the anti-aliasing is causing loopback devices to degrade, resulting in a loss of transparency at the system cache level and decoherence in the undelete function. This is only known to be a problem when the moon is gibbous.', NULL, NULL);
 INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (6, 4, 1, 'Sorry, it was SCO unix which appears to have the same bug. For a brief moment I was confused there, since so much code is known to have been copied from SCO into AIX.', NULL, NULL);
-INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (7, 5, 1, 'This would be a real killer feature. If there is already code to make it possible, why aren''t there tons of press announcements about the secuirty possibilities. Imagine - no more embarrassing emails for Mr Gates... everything they delete would actually disappear! I''m sure Redmond will switch over as soon as they hear about this. It''s not a bug, it''s a feature!', NULL, NULL);
+INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (7, 5, 1, 'This would be a real killer feature. If there is already code to make it possible, why aren''t there tons of press announcements about the security possibilities. Imagine - no more embarrassing emails for Mr Gates... everything they delete would actually disappear! I''m sure Redmond will switch over as soon as they hear about this. It''s not a bug, it''s a feature!', NULL, NULL);
 INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (8, 6, 1, 'Oddly enough the bug system seems only capable of displaying the first two comments that are made against a bug. I wonder why that is? Lets have a few more decent legth comments in here so we can see what the spacing is like. Also, at some stage, we''ll need a few comments that get displayed in a fixed-width font, so we have a clue about code-in-bug-comments etc.', NULL, NULL);
 INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (9, 10, 1, 'Initial bug report.', NULL, NULL);
 INSERT INTO public.messagechunk (id, message, sequence, content, blob, fti) VALUES (10, 11, 1, 'A test description', NULL, NULL);