User talk:Sbmeirow

From Wikipedia, the free encyclopedia
Jump to: navigation, search
The Signpost
25 February 2015

Menu[edit]

  1. My User Talk Archives
  2. My Awards and Barnstars
  3. My User Boxes
  4. My eBook Collection

TUSC token a513c889650ab4d3a2eefac4cd6cd5a6[edit]

Token for TUSC account!

TUSC token 171b95a178090101dc67a9f671fd2a4e[edit]

Token for TUSC account!

ARM Cortex-M[edit]

TI Stellaris Launchpad showing LM4F120H (ARM Cortex-M4F) MCU.JPG
Energy Micro Woder Gecko STK showing EFM32WG990F256 (ARM Cortex-M4F) MCU.JPG
Freescale FRDM-KL25Z board with KL25Z128VLK (ARM Cortex-M0+ MCU).JPG
NXP LPC800-MAX Board with LPC812(ARM Cortex-M0+ MCU).jpg

Can we have a new article ARM Cortex-M0 MCU core ? or We could merge ARM Cortex-M3 into a new article ARM Cortex-M - listing all Cortex M processor cores including Cortex M0. FossMCU (talk) 15:39, 5 December 2011 (UTC)

Yes, M0 and M4 needs to be addressed, but I haven't gotten around to do anything about them yet. I put the following in all the ARM talk section for discusion.
The popularity of the Cortex M0 and M4 are starting to take off, thus it would be easier to pick some direction before having a bunch of tiny articles. Should there be unique articles for each of the ARM Cortex families? Should there be only 3 major ARM Cortex articles instead, and redirect all sub-flavors to these 3 new articles? Requesting input at Talk:List of ARM microprocessor cores#Discusion for ARM Cortex article overhaul for comments! • SbmeirowTalk • 17:18, 5 December 2011 (UTC)
Do you need photos of ARM Cortex-M MCUs for this article. I have few NXP Cortex M3 and M0 MCUs, I can take photos. How about adding MBED image to this article? FossMCU (talk) 12:32, 13 December 2011 (UTC)
Yes, all of these articles need more photos: ARM Cortex-M, STM32, EFM32. The MBED photo doesn't show the part number on the IC, so I would say no. Any photos that we include, should CLEARLY show the vendor and part number on the IC chip. I need to find some time to take photos of all my ARM eval boards and chips on them. • SbmeirowTalk • 15:51, 13 December 2011 (UTC)
I will take photos of NXP LPC1114, LPC1343, EFM32 ICs. I also have LPC1343 LPCXPresso , EFM32 TG Starter Kit, MBED development board. The existing MBED does not look like CC-BY-SA. FossMCU (talk) 18:18, 13 December 2011 (UTC)
Uploaded [ARM Cortex-M] ICs, LPCXpresso photos. See my talk page. FossMCU (talk) 18:07, 14 December 2011 (UTC)
Uploaded ARM Cortex-M4F starter kits photos. Use these for Cortex-M4 section. See photos. FossMCU (talk) 06:46, 5 June 2013 (UTC)
Thanks! • SbmeirowTalk • 07:25, 5 June 2013 (UTC)
Cortex-M0+ dev board photo. Use it if relevant for the article. FossMCU (talkcontribs) 09:15, 20 July 2013 (UTC)
Another M0+ board FossMCU (talk) 05:15, 23 September 2013 (UTC)
GNU Tools for ARM Embedded Processors is by ARM Ltd not by Canonical. Launchpad is a platform offered by Canonical for FOSS development. See https://answers.launchpad.net/gcc-arm-embedded/+question/199912 #1 FossMCU (talk)

ARM[edit]

I just wanted to say that you have been doing some really nice work on the ARM pages, and that your efforts are very much appreciated. --Guy Macon (talk) 20:23, 6 April 2014 (UTC)

Thanks Guy! Thanks for all your edits too, because I see your edits in various technical articles too. I've done some editing on all the ARM articles, but its too much work to tackle all of them. I've done a lot, but still its barely a dent in where ARM articles need to end up. I'm mainly concentrating on lower-level microcontroller cores (Cortex-M) instead of higher-level microprocessor cores (Cortex-A) or (Cortex-A5x). I love microcontrollers, so that's where I'll invest most of my time in the ARM articles. I'll keep chipping away at them as I find time. • SbmeirowTalk • 21:01, 6 April 2014 (UTC)

See-also pseudoscience lists[edit]

A heads up that per MOS:SEEALSO, "As a general rule, the "See also" section should not repeat links that appear in the article's body or its navigation boxes." - if a pseudoscience-related article has the {{pseudoscience}} template at the bottom, then that already contains the List of topics characterized as pseudoscience link and you shouldn't repeat it as a see-also section. (If it doesn't have the template, then perhaps it should.) --McGeddon (talk) 11:57, 12 June 2014 (UTC)

Heads up per... "I didn't know that link was in the pseudoscience nav box"!!! Since multiple navboxes don't auto-expand, then I didn't know, nor have I looked at the contents of the pseudoscience navbox. The downside of navboxes that include the "kitchen sink" is people don't see the content of those navboxes because they aren't expanded, where they ALWAYS see wikilinks in "see also". • SbmeirowTalk • 19:51, 12 June 2014 (UTC)

Kansas small town populations[edit]

Thanks for correcting the mistakes I made while adding some population data to Kirwin and Galena. Besides, it felt sort of weird removing the note about the Decennial Census anyway.

Nonetheless, the way you corrected my mistake currently shows two external links after the population evolution chart: one of the original Decennial Census link, and the other being the Kansas population data pdf that I added. Another idea for that area of the population table is that the Decennial Census link can be kept as is, while the pdf I added could be a citation with a numbered footnote. Doyou think that's a good idea, or not so much? Mungo Kitsch (talk) 05:43, 15 June 2014 (UTC)

I haven't thought about it much and don't have an final answer at this late at night. I already saved your link in my notes at User:Sbmeirow/RecommendedChangesToArticlesFor2010Census so I could think about it some more before coming up with a new format before updating some cities. I was the person that manually updated every city in Kansas with 2010 Census data, and might do it again after the 2015 estimate is released. • SbmeirowTalk • 06:02, 15 June 2014 (UTC)

Pilger, Nebraska[edit]

I see that you've reverted my removal of the motto for Pilger, Nebraska, with the edit summary "whether you like it or not, it came from the official website".

I removed it because, at the time, there was no citation to indicate that it was from the official website. In my edit summary, I stated this: "Rm nickname as unsourced". You've fixed that by adding a citation.

I will continue to remove mottoes, slogans, nicknames, etc., if they don't carry citations. I have a great many Nebraska communities on my watchlist, and experience suggests that these lines in the infobox are magnets for vandalism, high-school humor, and OR. -- Ammodramus (talk) 22:33, 17 June 2014 (UTC)

You could've easily spent a few seconds checking their official website, but you didn't. Yes, I agree motto's, slogans, nicknames are easily vandalized and should be cleaned up. Still you should at least check the official website, because many times mottos are plain as day on a home page, but that is not always the case. I'll check the home page and quickly click around their website to find the quotes, and if I can't easily find it, then and only then will I delete it, otherwise I'll add a reference to prove it. • SbmeirowTalk
I'd be more inclined to invest the time and effort to search for a reference if I thought that the information was at all critical. Per MOS:INFOBOX, "the purpose of an infobox [is] to summarize key facts that appear in the article". I seriously question whether the nickname is a "key fact", and I note that it's almost never included in the body of the article. Unfortunately, there seems to be a tendency to design infobox templates with lots of lines, and then to fill in as many of the lines as possible. The result is that infoboxes all too often become lengthy compilations of minor details rather than brief summaries of the most essential facts in the article. -- Ammodramus (talk) 23:19, 17 June 2014 (UTC)

Solar Roadways[edit]

Thanks for all the work on Solar Roadways (company). I hate it when companies use Wikipedia for publicity purposes (although I'm not accusing them of doing this directly). Kendall-K1 (talk) 12:51, 26 May 2014 (UTC)

Thanks. Unfortunately, I wasn't aware of this article until I saw someone try to use a link to this article in a blog as proof of some cost estimate statements. If "Solar Roadways group/company" doesn't list the prices on their website, then all costs are considered speculation, thus those types of statements don't belong in the article. The article in now on my watch list, so I'll be watching all edits very closely. • SbmeirowTalk • 16:29, 26 May 2014 (UTC)
RfC
Solar Roadways

I am notifying everyone who participated in the Solar Roadways DRN that there is an open RfC at Talk:Solar_Roadways#RfC:_Should_the_cost_to_cover_the_entire_USA_be_included.3F. Thanks. -- GreenC 20:29, 17 June 2014 (UTC)

Blue Skyways unavailable?[edit]

It looks like the Blue Skyways website has been discontinued. Of course, that will affect the majority of KS-related articles. http://kslib.info/1013/Blue-Skyways-Transition - Gilliam (talk) 04:29, 6 July 2014 (UTC)

Yes it sucks. I assume most of them are archived on https://archive.org/ so look up the URL and fix links as you come across them. We can't do anything about it, except fix the links and find new links for each article. • SbmeirowTalk • 08:42, 6 July 2014 (UTC)
Today, I'm starting a multi-pass effort to cleanup county articles. I'll update one specific thing for each county on each pass, then start over and do the next thing. • SbmeirowTalk • 15:50, 6 July 2014 (UTC)

See also links[edit]

According to WP:SEEALSO, See Also sections are not supposed to include links that are already linked to from the article text: "As a general rule, the 'See also' section should not repeat links that appear in the article's body or its navigation boxes." Kaldari (talk) 17:24, 14 July 2014 (UTC)

Location-map captions[edit]

I notice that several of your recent edits to articles about municipalities, e.g. this one, have changed the location-map caption from "Location of X" to "Location of X within County and State".

Could I suggest that you use, instead, the more specific "...within Y County and (name of state)", like this? This gives the reader more specific information; and there are cases in which a community lies in more than one county, and the map only shows it in one (e.g. Emerson, Nebraska).

If you're disinclined to do this, could you please lowercase "county" and "state"? Per MOS:CAPS (which begins with the sentence "Wikipedia avoids unnecessary capitalization"), section "Institutions", such generic uses of the words should be lowercased. Thanks— Ammodramus (talk) 23:06, 15 July 2014 (UTC)

It should be like this article: Florence, KansasSbmeirowTalk • 00:45, 16 July 2014 (UTC)

Kansas census-designated places[edit]

Hi-User:The Catalyst31 has a list of census-designated places and there is one census-designated place in Kansas that needs an article. Wilroads Gardens in Ford County, Kansas. I thought you might be interested since you have done articles about unincorporated communities in Kansas. Thanks-RFD (talk) 12:40, 7 August 2014 (UTC)

I can't find the user, but I'll try to find some time on the article. • SbmeirowTalk • 07:12, 8 August 2014 (UTC)
Done. • SbmeirowTalk • 06:09, 13 August 2014 (UTC)
Many thanks for doing the article-RFD (talk) 10:52, 14 August 2014 (UTC)

ESU Athletics article[edit]

Hello. Since you have made some edits to the article, I was wondering what you thought about a requested move on the ESU Hornets page? I moved it without a consensus, and it's been reverted back (I know I did it without it being discussed), but I really think that the "Lady Hornets" should be used in the title. Thanks, CorkythehornetfanQuestion? 02:14, 23 August 2014 (UTC)

Looks like my opinion varied from yours. I think the article title should be short and generic like "Emporia State Sports", but I don't think this is typical on other colleges. • SbmeirowTalk • 02:34, 23 August 2014 (UTC)
That's fine.. I just wanted other opinions! I agree about the "sports" thing, though. It would definitely make it easier! I'm just not sure all Wikipedians would agree. CorkythehornetfanQuestion? 02:42, 23 August 2014 (UTC)

A barnstar for you![edit]

Special Barnstar Hires.png The Special Barnstar
I'm awarding "The Special Barnstar" because since I joined Wikipedia, you have helped me a lot. From starting my user page to giving me suggestions, and a whole lot more... the list could go on! Wikipedia should be proud to have an editor like you! Thanks, Corkythehornetfan (Talk) 23:15, 28 August 2014 (UTC)
Thanks! • SbmeirowTalk • 08:13, 28 September 2014 (UTC)

Emporia State University[edit]

Hello! I was wondering what your thoughts were about the Emporia State University article? What needs improvement? What should be removed or added? Things like that... I'm running out of ideas! I have my opinions on what I've added that I think may need removed, but seeing what others say will help out with my opinions. Your help would be much appreciative! Corkythehornetfan (Talk) 04:31, 9 January 2015 (UTC)

I'm not a college article expert, but I feel a college article should be useful to high school students and parents that are looking for a college, so think about that type of approach too. Maybe add a table about the dorms, like at University_of_Kansas#Student_and_faculty_housing. The Foundation section should be tweaked, because the long subsection name should be removed as a subsection or renamed to "campaign" or something more generic. If you can find an official campus PDF map (that lists the name of each building), then add it to the external links section. Look at college article in other states, especially along the coasts to see what they include in articles. • SbmeirowTalk • 20:41, 9 January 2015 (UTC)
Okay, thanks! The foundation section was one opinion I had, especially the name. I'll also add the map of the campus. I never thought of the "high school students and parents" approach.. I'll definitely keep that in mind! Thanks again, Corkythehornetfan (Talk) 22:15, 9 January 2015 (UTC)

WP:OVERLINK[edit]

Please review this Wikipedia policy. We do not link ordinary English words, and we don't link the same things repeatedly. Ground Zero | t 22:25, 9 January 2015 (UTC)

Please remind youself to leave a link to the article in question. • SbmeirowTalk • 01:54, 10 January 2015 (UTC)
This was a general comment as it seems that you edited several articles in this way, including: Ottawa County, Kansas, Sedgwick County, Kansas, and Saline County, Kansas. Ground Zero | t 16:59, 10 January 2015 (UTC)
Thank you. • SbmeirowTalk • 20:22, 10 January 2015 (UTC)

Rollback rights[edit]

I was surprised you didn't have that already. Rollback vandalism when looking at the last diff in the edit history.– Gilliam (talk) 14:53, 17 January 2015 (UTC)

County navboxes[edit]

County navboxes are solely meant for locations within the county: municipalities, minor civil divisions, and unincorporated communities. These lists are none of those things. Nyttend (talk) 13:18, 3 February 2015 (UTC)

Where is the "County navbox" guideline? • SbmeirowTalk • 13:22, 3 February 2015 (UTC)
Here. County templates are always used for things related to the county, and state templates for things statewide. Nyttend (talk) 13:40, 3 February 2015 (UTC)
Ok. • SbmeirowTalk • 13:49, 3 February 2015 (UTC)

What's your definition of a microarchitecture?[edit]

Given that you're classifying cores with quite distinct internal designs as having the ARMv7-A or ARMv8-A "microarchitecture", your definition must be different from the one used in the microarchitecture article ("the way a given instruction set architecture (ISA) is implemented on a processor"). What definition are you using, and what does that make the instruction sets of the cores in question - AArch{32,64}? A{32,64}? ARM's not different from other ISAs here - there's the ISA specification, independent of the organization of the system blocks used to implement it, and there are the implementations, just as there are for System/3x0, x86, SPARC, MIPS, Alpha, etc., etc.. Guy Harris (talk) 23:19, 9 February 2015 (UTC)

Per my comment in that User Talk section, I meant that ARMv7-A is an ARM architecture and NOT an instruction set, to ensure that readers don't think they are the same thing. ARM has many different instruction sets and instruction extensions, and a specific subset are grouped together for an ARM architecture. The big problem is that ARM cores have flexibile options that allows IC manufacturers to DISABLE some instructions, which makes it even harder to describe. I might be over aggressive on my statements, but I'm still correct that everyone needs to be careful how "ARMv7-A" is used in descriptions. • SbmeirowTalk • 00:08, 10 February 2015 (UTC)
OK, so the "ARM® Architecture Reference Manual ARMv7-A and ARMv7-R edition" section A4.1 "About the instruction sets" says:
ARMv7 contains two main instruction sets, the ARM and Thumb instruction sets.
and in section A1.3 "Architecture versions, profiles, and variants" says:
ARMv7 provides three profiles:
ARMv7-A Application profile, described in this manual:
  • Implements a traditional ARM architecture with multiple modes.
  • Supports a Virtual Memory System Architecture (VMSA) based on a Memory Management Unit (MMU). An ARMv7-A implementation can be called a VMSAv7 implementation.
  • Supports the ARM and Thumb instruction sets.
so presumably all cores implementing the ARMv7-A architecture should list "ARM" and "Thumb" for its instruction sets, and can also list Jazelle or ThumbEE if they implement them.
The "ARM® Architecture Reference Manual ARMv8, for ARMv8-A architecture profile" speaks of "The AArch64 Instruction Set" in Part C but then starts talking about the "A64" instruction set, and speaks of "The AArch32 Instruction Sets" in Part F, with those instruction sets being "T32" and "A32", so presumably "The AArch64 Instruction Set" means "the instruction set included in AArch64" rather than "the instruction set named AArch64", that instruction set being "A64". So presumably cores implementing the ARMv8-A architecture have A64 and possibly also A32 and T32 as instruction sets.
(In any case, none of ARMV{7,8}-{A,R,M} are microarchitectures. The microarchitecture of, for example, Cortex-A15 is the Cortex-A15 microarchitecture, unless multiple different cores share the same microarchitecture.) Guy Harris (talk) 01:13, 10 February 2015 (UTC)
Yes, for all of the 64-bit cores it a lot easier to describe instruction sets, because I think both AArch32 and AArch64 exist in core, and you are executing either one or the other depending on which rights a specific "task" (not the correct term) is allowed". I'm glad that ARM starting grouping everything together into new names, such as AArch32 and AArch64, because its less confusing! • SbmeirowTalk • 01:41, 10 February 2015 (UTC)
I'm pretty sure that AArch32 can't be used to describe 32-bit-only ARM Cortex-A cores, because they aren't the same. • SbmeirowTalk • 01:41, 10 February 2015 (UTC)
So ARM has:
  • The "ARM architecture", which has multiple numbered versions and, for ARMv7 and ARMv8, multiple profiles (A, R, and M for v7, and A and R for v8);
  • For ARMv8-A, AArch64, an entity of some sort with no obvious noun or phrase used for the category to which it belongs, which has an "Application Level Architecture", an "Instruction Set" (A64), and a "System Level Architecture", and AArch32, a similar name with no obvious category, which has an "Application Level Architecture", two "Instruction Sets" (A32 and T32), and a "System Level Architecture";
  • For ARMv7-{A,R}, multiple instruction sets (ARM, Thumb, ThumbEE - Jazelle appears to be deprecated);
and so on. So ARMv[3-8] are versions of the ARM architecture, but aren't instruction set architectures, as they include multiple incompatible instruction sets and encodings, and ARMv[3-8]-[ARM] are profiles for those architectures.
Unfortunately, the "arch=" parameter in the infoboxes for processors has a tag of "Instruction set", so it's not entirely appropriate for ARMv[3-8]-[ARM], and the best you can do, if you don't want to just ue the architecture+profile, is enumerate the instruction sets and perhaps put the architecture version+profile in parentheses after the enumeration. Guy Harris (talk) 02:04, 10 February 2015 (UTC)

EXAMPLE 1 - Let me step back in history just a little bit, lets take the ARM7TDMI core, it has both the ARM (32-bit) instruction set and Thumb (16-bit) instruction set in the same core. You can ONLY use one or the other instruction set, but NOT both at the SAME time. You have to go through a special step to move between these two instruction sets. One of the crazy things it that all interrupts force you back into ARM instruction temporarily then when it ends you go back to the previous instruction set, whether ARM or Thumb. Depending on the compiler, if your main program is compiled for Thumb instruction set, you may have to put your interrupts in another file and compile them for ARM instruction set, or better compilers you do something special in the C code to force an interrupt function into ARM instruction set. • SbmeirowTalk • 01:28, 10 February 2015 (UTC)

EXAMPLE 2 - I think all the cores that have Jazelle instruction sets are "toggled" kind of like my above ARM7TDMI example. You only execute one instruction set at any point in time, otherwise you have to switch over to a completely different instruction set. • SbmeirowTalk • 01:32, 10 February 2015 (UTC)

EXAMPLE 3 - All of the Cortex-M cores are different than the ARM7TDMI. Though a specific Cortex-M core has different combinations of various instruction sets, they ALL are combined together and exist at the same time. NO alternate instruction set to toggle into. • SbmeirowTalk • 01:32, 10 February 2015 (UTC)

Yes, just as the processor in the machine on which I'm typing this has two instruction sets in the same core, which can't, as far as I know, both be used at the same time - the "long mode" instruction set and the "compatibility mode" instruction set. Yes, the "long mode" instruction set and its encoding is, 99 44/100% of the time, a straightforward superset of the "compatibility mode" instruction set but, as I remember, there's one prefix byte that's interpreted differently in long mode and in compatibility mode.
The difference here is that the A64, "ARM"/A32, and Thumb/Thumb-2/T32 instruction sets have completely incompatible encodings, so the mode bits have a bit stronger effect, and people might be more willing to call x86-64 an instruction set (the instruction encoding differences between long and compatibility mode nonwithstanding) than to call ARMv8-A an instruction set. System/3x0 also had mode bits, but they affected instruction behavior rather than instruction encoding, e.g. whether, in 32-bit code, the upper 8 bits or the uppermost bit of an address were ignored.
The VAX offered a PDP-11 compatibility mode as well; that's more like ARM, but I don't know whether DEC considered the compatibility mode to be part of the VAX architecture or not. Guy Harris (talk) 01:50, 10 February 2015 (UTC)
Back to the ARM7TDMI discussion... at a previous employer, we started with ARM instruction set and continued to use it until we ran out of memory. We couldn't go back and rev boards, so we were forced to move to thumb instruction set, and switch to ARM instruction set in a few custom algorithms that did lots of math. By switching over to thumb, we recovered enough memory to finish the project on that board. • SbmeirowTalk • 02:07, 10 February 2015 (UTC)
All the licensed cores with lots of flexibility to enable/disable features are a completely different mess compared to Intel or AMD. Though Intel and AMD have some common instruction sets and instruction extensions they are going down slightly different paths. ARM is crazy because ARM throws stuff over the wall to silicon makers and they get to pick and choose any darn combination they want to implement in their silicon, so a core from one silicon maker may have a different set of enabled features than a core from another silicon maker. • SbmeirowTalk • 02:07, 10 February 2015 (UTC)
One of the other problems we run up against is "microarchitecture" vs "ARM architecture", and "CPU" vs "ARM core". We can't completely ignore the terms used by "ARM Holdings", because "ARM architecture" and "ARM core" is what they use in all their documents. • SbmeirowTalk • 02:07, 10 February 2015 (UTC)
Microarchitecture vs. ARM architecture is a solved problem. A microarchitecture is what it says on the box in the article; it's "the way a given instruction set architecture (ISA) is implemented on a processor." None of ARMv[3-8] are anything like that nor are any of ARMv[78]-[ARM]; it's not what instruction encodings it accepts, it's now it decodes and executes those instructions.
The "ARM architecture" has multiple versions, that being the "v[0-9]" after "ARM". Some of those versions specify multiple instruction encodings, hence multiple instruction sets. Those instruction sets, like other instruction sets, have both "base" and "additional" features. For most other instruction sets, the "additional" features are new features added to the instruction set, with newer processors implementing the new features; for ARM, some of them are optional features licensees may or may not implement in particular cores. (In the old days, more ISAs had optional features, such as floating-point instructions, but, for general-purpose computing, it's more trouble than it's worth to offer processors without the additional features these days.) Perhaps one ARMv7-A core has VFP and/or Advanced SIMD and another doesn't, but, well, ARM's own documentation for the ARMv7-{A,R} architecture describes them as OPTIONAL, so they're just like floating-point in System/360 or in x86 prior to the Pentium. Guy Harris (talk) 02:37, 10 February 2015 (UTC)

Infobox discussion[edit]

I disagree how you are approaching the infoboxes. Instruction set edits are fine, but the "ARM architectures" need to be listed. • SbmeirowTalk • 02:20, 10 February 2015 (UTC)

Then list them under "arch=" - for example, in parentheses, as I think I suggested somewhere. They are NOT microarchitectures, and must not be listed under "microarchitecture="; as I said, "microarchitectures" vs. "ARM architecture" is a solved problem - they are two different things, with the only thing they have in common being the letters "a", "r", "c", "h", "i", "t", "e", "c", "t", "u", "r", and "e", in that order. A microarchitecture for an ARM core implements some particular version and profile of the ARM architecture, with some particular possibly-empty and possibly-improper subset of the OPTIONAL features for that version/profile. Guy Harris (talk) 02:40, 10 February 2015 (UTC)

Wikipedia Library Newspapers.com signup[edit]

Hi Sbmeirow,

Thanks for applying for one of the free Newspapers.com accounts at the Wikipedia Library. Your application had been pending since last August because we had more applicants than accounts, but we have just been given more accounts and you have been approved. However, one of the requirements for an account is that you have your preferences enabled to receive email messages on English Wikipedia. I need to email you a very short signup form to fill out. Would you mind changing your preferences so I can do that, please? Your email address (and no other information) will be passed on to Newspapers.com so they can activate your subscription. If you're no longer interested in Newspapers.com, please let me know. Thanks! HazelAB (talk) 18:41, 25 February 2015 (UTC)

Wikipedia email re Newspapers.com signup[edit]

Mail-message-new.svg
Hello, Sbmeirow. Please check your email – you've got mail!
It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{YGM}} template.
HazelAB (talk) 14:05, 26 February 2015 (UTC)