Learn LISP

Welcome to the SICP Web Site

WERD in Atlanta
Courtesy of Robert W. Woodruff Library Archives, Atlanta University Center
Jesse B. Blayton Sr.
became the first radio station in America to be owned by an African American when Jesse B. Blayton, a professor at Atlanta University and a bank president, bought it in 1949 and hired his son, Jesse Blayton Jr., as station manager. The 1,000-watt station, purchased for $50,000, was located in the Prince Hall Masons Grand Lodge at 334 Auburn Avenue.

Jesse Blayton Jr. hired veteran disc jockey Jack Gibson as announcer and replaced the rest of the all-white staff with black announcers. The station's "Four Horsemen"—Gibson, Joe Howard, Roosevelt Johnson, and Jimmy Winnington—played music and other programming of interest to black listeners. Gibson was a popular on-air personality, perhaps the city's leading disc jockey at the time. Blayton also hired Ken Knight as program director.

The Masonic
Courtesy of Special Collections & Archives, Georgia State University Library
Prince Hall Masonic Lodge
lodge that housed WERD was also home to Martin Luther King Jr.'s Southern Christian Leadership Conference (SCLC) during the 1960s. It has been said that King would bang on the ceiling with a broomstick when he wanted to make a public statement, and the WERD disc jockey upstairs would lower a microphone from the window above.

Blayton Sr. sold the station to white owners in 1968. He remained active in community affairs until his death on September 7, 1977, and was inducted into the Radio Hall of Fame in 1995.

Werd!

New Georgia Encyclopedia: WERD

The Subversion open source community does not provide binaries, volunteers make them. CollabNet makes available CollabNet Subversion, which is Subversion compiled, tested and certified by CollabNet. Additionally, here on openCollabNet you can download binaries that were contributed by community members.

Subversion Binaries

She typed in 'God damn clippy'

Sorting It All Out : She typed in 'God damn clippy'

This is a collection of the wisdom posted on the internet by a guy calling himself Gecko45. It all started back at the end of the halcyon summer of 2001, and his posts have created a certain urban legend that many refer to as the Mall Ninja. Hang out at any gun shop, gun show or shooting match and you’ll see one of these guys–you might even see a group of them since they are known to associate in the wild.

The Mall Ninja is easily distinguished by an abundance of “tactical” gear, such as fatigues, a thigh holster (with, of course, a Glock), combat boots, bandolier and other accouterments that you’d usually only see on a SWAT operative. Median age is usually 19-25, and they tend to boast about their various exploits with certain Special Forces units, all of which they’re too young and idiotic to have joined (real Special Forces types don’t brag). They typically have opinions on everything, regardless of expertise, they are uniformly poor shots, and they tend to exhibit a frightening lack of safety training.

The shadowy and shrill figure known as Gecko45 is the holy Dalai Lama of these dolts, but trust me, there are more. Many, many more.

Shrine of the Mall Ninja » LonelyMachines

While pirates were certainly cruel and violent criminals, pirate ships were hardly the floating tyrannies of popular imagination. As a fascinating new paper (pdf) by Peter Leeson, an economist at George Mason University, and “The Republic of Pirates,” a new book by Colin Woodard, make clear, pirate ships limited the power of captains and guaranteed crew members a say in the ship’s affairs. The surprising thing is that, even with this untraditional power structure, pirates were, in Leeson’s words, among “the most sophisticated and successful criminal organizations in history.”

The Pirates’ Code: Online Only: The New Yorker

Anyone who has watched Disney's "Pirates of the Caribbean" knows all about the Pirate Code, laid down by the pirates Morgan and Bartholomew. I think the idea of a single code for pirate is probably the most modern piece of Pirate Mythtory to be featured on this site, and I don't think it extends back any further than the release of the excellent POTC.

The Pirates' Code

The repository and its children matter because they preview this world to come. Graham promised parents smarter, better children than they could have naturally. He used the best science of his time (sperm storage and artificial insemination) to preserve and replicate what he saw as the most valuable genes in the world. New-genics will try to do much the same thing—though more precisely, more microscopically, more scientifically.

Genius Sperm

On September 3, 2004, a nine-member officer's panel at Fort Lewis, Washington, found Specialist Ryan G. Anderson guilty of five counts of seeking to aid the enemy during a time of war and attempted espionage. The court martial subsequently sentenced him to five concurrent life terms for his crimes. To date, the sentence represents the most severe penalty meted out to a U.S. citizen in President George W. Bush's global war on terror. The case also marked the triumph of the new field of cyber counterterrorism, which I helped develop. Working from my home computer, I enabled Anderson's capture. There have since been more than 200 other cases although many of these were intelligence cases that, for various reasons, did not result in criminal prosecution.

I haven't read this, but need to remember to do so.

My Cyber Counter-jihad - Middle East Quarterly

We all make mistakes. Wouldn't it be great if life always gave you a second chance or an opportunity to correct those mistakes? Fortunately when you are using Subversion you can always correct a mistake, in most cases, you can correct those mistakes quite easily.

So let's start with one mistake that Subversion does not allow you to do easily, and that is remove all traces that something ever happened. Subversion records the way your repository exists at a point in time, and that history is immutable, which means it can never be changed. Unfortunately this means that if you accidentally commit your password in a configuration file, you can edit the file and commit it again, but Subversion will forever retain that original commit, including your password. The only way to truly remove something from a repository is to dump the repository to a file, carefully remove the parts you do not want from the dump file, and then reload the repository. This is not for the faint of heart, but it can be done. It is worth pointing out that most Subversion installations use a commit hook to send email messages with the details of each commit. Even if Subversion made it easy to remove traces of something from a repository, in the case of something like a password, there is no way to undo the fact that it might have been emailed all over the world.

A common mistake that Subversion can easily fix is the recovery of something that you deleted. I hate to admit it but a few months ago I accidentally deleted the entire branches folder in the Subclipse repository. You can see the gory details of the commit in ViewVC here. Fortunately, I knew that I could easily get it back. If you looked at the previous link, you would see that I committed the deletion of the branches folder in revision 2981. So to recover the folder, all I had to do was copy it as it existed in revision 2980.

svn copy -r2980 http://subclipse.tigris.org/svn/subclipse/branches@2980 \
http://subclipse.tigris.org/svn/subclipse/branches

This command says, "Copy the branches folder as it existed at revision 2980 to a folder named branches (which does not currently exist)." You have to add the @2980 to the first URL to help Subversion's history tracing algorithm find the folder. If you leave off that parameter then Subversion would look in the HEAD revision of the repository to find the folder, but we know that it does not exist any more at HEAD. You can see the results of this commit in the ViewVC history here. Notice that it shows the item was added by copying it from revision 2980.

So that is how you can recover something you deleted. What about something more subtle like changes to a set of files that was valid, but now you have decided you no longer want those changes. You essentially want to "undo the commit" that made those changes. This is actually very easy to do in Subversion, even if there have been subsequent changes made to the same file, by doin... [ Read More (0.1k in body) ]

Submerged - Subversion Blog - Second Chances and Subversion...