text:
UPDATE! - We will be previewing most of the lots on Tuesday, July 9th 4pm-7pm. The address is 10508 Bondesson Circle Omaha, NE. "S" lots and "B" lots are in another location and there will not be a preview of those items/equipment. Note: "B" lots are not located at Bondesson Circle. Address will be given to winning bidders. Blocks are in varying conditions. First come, first served on pickup day. Blocks are not assigned by lot number.
Pickup for items at Bondesson Circle will be 9am to 3pm Friday July 12th. Pickup for Salt lot items (lots begin with S or B) will be Saturday July 13th from 9am to 3pm. Please plan ahead for pickup. Additional dates and times will not be available.
This auction is available on Proxibid.
To bid, please click here: Auction Solutions, Inc Auction Catalog - NMB Equipment Liquidation Online Auctions | Proxibid
NMB Enterprises Liquidation Auction
Regardless of the business season: winter, spring, summer or fall, this auction covers it all. NMB Enterprises Liquidation Auction offers equipment and tools for all four seasons, from lawn care to snow removal and jobs in-between your needs are covered!
Please be aware that Auction Solutions Inc. does not provide boxes, carts, tools, or dollies to move auction items. Pick-up of larger items will require you to bring a partner to load your items, as Auction Solutions Inc. staff will not be available to help with loading or unloading.
All lots not starting with a B, or a S will be available for pickup on Friday the 12th of July 9 am to 3 pm.
Lot items that start with a B, or a S will need to be picked up on Saturday the 13th of July 9 am to 3 pm.
Pickup address will be released to winning bidders after the auction ends.
Descriptions entered are to the best of Auction Solutions Inc.'s ability. No guarantees or warranties will be given or expressed on any items. All items from Auction Solutions Inc. are sold as-is, where-is, meaning items will not be fixed, cleaned, detached, unhooked, or moved before or after sale.
Please note Auction Solutions Inc. staff are not responsible for auction winnings post pick-up. You must make sure that all auction items are accounted for. Once those items are signed for and removed, there will be no refunds or discounts.
If items need to be transported from an offsite pick-up to our office for pick-up there will be an additional fee of $40.00 and would need to be picked up within one weeks time. If items are in office up to 7 days, a daily $15.00 will be added each day and will be forfeited after the 7 days. For all auctions, if items are not picked up within the 7 day time frame, items will be forfeited and no returns will be given. If your payment is declined, you will have 7 days to pay for items and pick them up. If items have not been paid for and have not been picked up within the 7 day time frame, your items will be forfeited. Furniture, motors, cars, and other large items will not be transported from offsite pick-ups for any reason and will not be offered for shipping.
Auction Solutions Inc. will be issuing email notifications from Shipping Saint within 2 days of auction ending, and it is required that the winner of the lot select between the available choices of shipping or in-person pick-up, or you will not receive your item. If you have any shipping questions, please respond directly to the message from Shipping Saint and one of our employees will respond in a timely manner.
Agreement to terms: By bidding in this auction, you are agreeing to all terms and conditions for this auction.
Credit cards on file will be charged within 24 Hours of the auction completion. A wire transfer will be required for purchases of $5,000.00 or more. Numismatic buyers with purchases of $750.00 or more are asked to contact our office for payment options. Merchandise must be paid for in full prior to being removed or picked up from the auction site.
Declined Cards are subject to a $35.00 transaction fee, and the potential inability to bid on future auctions. Buyer's Premium and tax are listed elsewhere. To be considered tax exempt, Auction Solutions, Inc. must have a SIGNED Nebraska form 13 on file. Auction Solutions Inc. shall attempt to describe merchandise in advertising and on the internet, but makes no representations or warranties, expressed or implied. In no event shall Auction Solutions Inc. be held responsible for having made or implied any warranty of merchantability, or fitness of an item for a particular purpose. Off-site bidders understand and acknowledge they are not able to inspect items as if they were to examine them in person. It is the bidder's responsibility to further inquire to determine condition, age, genuineness, or any other determinative factor. Bidders shall be the sole judge of value.
When your items are ready to be shipped, we will notify you through Shipping Saint. Your items will be shipped once the Shipping and Handling fees are fully paid. To avoid extra costs and shipping delays, please ensure that your billing, shipping, and credit card information are accurate on your account. Please note that shipping is not available for storage unit auctions. For firearms, coins, and jewelry, shipping is handled internally at Auction Solutions Inc.
If your purchase requires freight transport (e.g., LTL or OTR Carrier), please contact our office to create arrangements. Vehicle titles will be held until payment clears, and if the title is held by a bank, it may take over 30 days to obtain a clear title. If you have any questions, feel free to reach us at 402-571-0393.
If you are outside the Omaha Metropolitan area and plan to pick up your items or have someone pick them up on your behalf, please adhere to the specified pick-up time and requirements. Picking up items outside the scheduled time may incur additional fees. Winning bidders will receive an email with pick up dates and location, with their paid invoice. Please refer to auction details for specific dates and times. Be sure to plan to pick items up during this time frame. If alcohol or firearms are being picked up, the name on the invoice must match the identification or permits. If employees need to return items to the office for pick up, an additional fee will be charged based on the quantity of items being brought back. Please note that furniture and large items will not be transported by employees. Once items are picked up, there are no further negotiations or discounts available.
All information contained herein is believed to be accurate to the best of our ability but is not guaranteed. The Auction Company may rescind the sale of any item(s) within 30 days if it is determined the lot was sold in error, or that removal would be impossible, impractical, or disruptive to the rights of the seller, or other third party. Items not claimed within 5 days of the auction close will be considered abandoned; a 20% re-stocking fee will be assessed, and the item(s) repurposed. NO REFUND WILL BE ISSUED. All property is sold "AS IS", WHERE IS and ALL SALES ARE FINAL.
Shayne Fili Professional Auctioneer
Office Phone: 402-571-0393.
All lots not starting with a B, or a S will be available for pickup on Friday the 12th of July 9 am to 3 pm.
Lot items that start with a B, or a S will need to be picked up on Saturday the 13th of July 9 am to 3 pm.
Pickup address will be released to winning bidders after the auction ends.


text:
191 Vascular & Endovascular Surgery Conference: M&M (121916)
The Vascular Surgery Conferences are designed to update and review the participants in vascular surgery.
Target Audience
Practicing vascular surgeons, interventional radiologists, community physicians and faculty, residents in training, fellows, medical students and other interested health care professionals.
Learning Objectives
At the conclusion of this activity, the participant should be able to: 1) Better understand the pathophysiology, diagnostic testing, and management options (medical, surgical, and endovascular) in dealing with the patient and condition presented, as well as to be aware of recent clinical and research advances in the surgical areas listed above; 2) Better understand the basic science and mechanisms of disease associated with various vascular pathologic states as well as to apply current treatment approaches to their clinical practice; and 3) Better understand the pros and cons of current literature on a specific vascular disease topic as well as to formulate optimal conclusions based on consensus.
Available Credit
- 1.00 Attendance

subset: commoncrawl


text:
Leiden University
People have become more critical of EU policy and often seem to prefer local policy solutions in response to globalisation problems. How do you experience EU policy? Does it help? And if not, how can we change this? In this course, we learn how the European Union prepares and decides on policy, and how policy is transferred to member states and implemented by various authorities, including regional and local governments. We discuss the challenges of the European multi-level governance structure. We also focus on the main causes of policy failure or success. On this journey, we focus on actual policy and present the views of various experts: how easy is it to establish yourself in another EU-country? How do governments make sure that the air you breathe is clean? And who is responsible?
You will be able to do research together in your own local setting. Research on implementation in which you can make comparisons between different countries or areas. If you live outside the EU, this is not a problem. We have developed assignments in such a way that you can do research in your area and compare your findings with others.
This MOOC has been rated as one of the best MOOCs of 2017 and is currently in the Top 50 MOOCs of All Time of Class Central
So, are you curious? Please join: 'EU policy and implementation: making Europe work'. Watch our trailer video at https://www.youtube.com/watch?v=n3nSN9R3VR4
Specific details
Category of Education
Social Science


text:
Looking for a trusted source to buy PLC Control Panel In Gurdaspur? Brilltech Engineers Pvt. Ltd is the one you can reach. We have a highly experienced team, well-loaded manufacturing unit and a lot more to match up the ever-evolving needs of our customers. Moreover, our focus on maintaining high quality and attaining customer satisfaction stands us ahead of the curve.
As one of the best PLC Control Panel Manufacturers in Gurdaspur, we are trusted by people not only within the boundaries but even beyond that. Our custom-based products are able to match up your distinct needs. Our products are known for their sustainable performance and all the other features that it offers.
Being one of the paramount PLC Control Panel Exporters and Suppliers in Gurdaspur, we are not only here for delivering the best quality, but also delivering it at the right time. So, send us your enquiry or call now to place your order with us.
Need A Query
If you are looking for premium quality PLC Control Panel In Gurdaspur that gives you excellent performance, then you are on the right page. Brilltech Engineers Pvt. Ltd. is one of the eminent PLC Control Panel Manufacturers In Gurdaspur that deals in a wide array of PLC Control Panel with different specifications. We have an in-house manufacturing unit where we design products with utmost precision. We use cut-edge tools and modern machinery to manufacture premium quality Electrical Panels, LT Distribution Panels, Cable Bus Ducts, Power Generators, and Electrical Transformers in Gurdaspur. We supply genuine grade PLC Control Panel in Papua New Guinea, Poland, Anantnag. Our highly trained and experienced professionals never mind working beyond boundaries in bringing safe and precise PLC Control Panel In Gurdaspur.
An electrical panel is a box made up of metal and has a door. You'll find all your home's breaker switches in this panel. It shuts off automatically when more current run through them. If you are looking for Electrical Panel, we have LT Distribution Panel, Load Management Panel, Outdoor Power Panel, Marshalling Panel, and Power Control Panel In Gurdaspur. So get in touch with us for your Panel need.
An electrical cable is a current-carrying assembly of wires that runs side by side and are bonded and twisted. They are used to carry current. We, one of the leading Electrical Cable Manufacturers In Gurdaspur, offer you top-quality Electrical Cable In Safdarjung, Dholpur, Tiruvarur.
Chemical Earthing is a traditional earthing system that improves the condition of the soil and decreases soil resistivity. If you once installed, Chemical Earthing can serve for years and years. If you are looking for Chemical Earthing In Gurdaspur, we are here to help you by delivering the best GI Earthing Strip, Copper Earthing Strip, Conventional Earthing, and Maintenance Free Earthing in Gurdaspur for you.
The transformer is an electrical device. It is designed to transfer electrical energy from one electrical circuit to another, either stepping up or down the voltage. So get the best quality PLC Control Panel In Ruwais, Khammam, Kushinagar from us in a call. We, one of the reliable Transformer Manufacturers In Gurdaspur, are here for you.
The generator set is a combination of generator and engine. It is an engine that drives the generator, and supply power is used to run other equipment. We offer Diesel Generator Set, Silent Generator Set, Gas Generator Set, Mobile Generator set and Power Generator Set In Gurdaspur that is easy to install, so make your order from us now.
Bus-Duct is a sheet metal duct in the electric power distribution and is used to conduct electricity to power cables or cable buses in commercial and industrial settings. We, one of the Bus-Duct Manufacturers In Gurdaspur, are here to customize them according to your requirement. So for Bus-Duct in Iowa, Sangrur, Dharmanagar, we are a one-stop station for you.
A cable tray is an assembly of units that have associated fittings that form a rigid structural system. It is used for securely fastening or supporting cables. Whether you want Galvanized Cable Tray, Ladder Cable Tray, Perforated Cable tray, and Race Ways, we have all of them under a roof. So rely on us for the best quality Cable-Tray In Gurdaspur.
Our customers have so many questions in their mind and here we tried our best to answer the most common ones.
Established in 2007, Brilltech Engineers Pvt. Ltd. is excellently dealing in a huge array of Panels, Electrical Cables, Chemical Earthing, Transformers, Generator Sets, Bus Ducts, and Cable Trays. An ISO 9001:2008 certified company is involved in the business of manufacturing, suppling and exporting of the entire range. Mr. Nitin Pratap Singh is the honorable Chairman, whose endeavors have made the company competent to serve some major clients like Godrej, Park Plaza Hotels & Resorts, RG Group, Shapoorji Pallonji, Tata Housing, Honda, British Council, Hero, Jaquar, Samsung, Bosch, and many more.
The commitment to quality and technical competence is something that make Brilltech Engineers Pvt. Ltd. PLC Control Panel standout from the crowd. The company is also appreciated for its product design and around-the-clock-support. Professionals are appointed to meet your queries.
The product range offered by Brilltech Engineers Pvt. Ltd. is very huge and vast. The company deals in all types of Panels, Electrical Cables, Bus Ducts, and Cable Trays. In addition to this, the company also specializes in the dealing of Transformers, Generator Sets, and Chemical Earthing Solutions.
You can reach us at Plot No. 58, Ecotech-12, Noida Extension. -201310, NCR - Delhi, India. Also, you can fill the enquiry form available on the website to buy the PLC Control Panel.
The state-of-the-art infrastructure includes a well-equipped in-house manufacturing unit, which is backed with modern machines and technology. Thus, Brilltech Engineers Pvt. Ltd. is praised for delivering PLC Control Panel that comply with the international quality standards.
Although, Brilltech Engineers Pvt. Ltd. is praised to deliver defect-free PLC Control Panel and quality services, there could be chances that you find some complain. You can place the complaint regarding the same here.
You can make your query by simply filling the query form on the Contact Us page. You can call on +91-9818292266, +91-9870573334, +91-9870573335, on Mon - Sat 8:00 AM - 6:00 PM. You can also drop an email at email@example.com. Apart from that, you can also WhatsApp us about your query.
We have carved a niche as one amidst the top-notch PLC Control Panel manufacturers in India. The PLC Control Panel is manufactured as per the international quality guidelines complying to ISO certification. Along with this, the team of experts is also appointed to help with the after sales services. with dedication and customer centric approach we have accomplished more than 900 plus projects and received support from more than 500 satisfied clients.


text:
The Census Bureau announced Monday that it would drop the word "Negro" from its forms, after some described it as offensive. According to the Associated Press, the term will be replaced next year by black or African-American. From the AP:
"The change will take effect next year when the Census Bureau distributes its annual American Community Survey to more than 3.5 million U.S. households, Nicholas Jones, chief of the bureau's racial statistics branch, said in an interview."
AP reports that the term was first used in the 1900 Census, and back in 2010, a bureau public information officer told us that the word had been on Census forms since about 1950.
But the bureau and the Census Director's Blog decided to tackle the issue after many African-American people complained about it during the 2010 Census.
"The category 'Black, African Am., or Negro' was used in Census 2000, based on research in the late 1990s that showed there was an older cohort of African-Americans who self-identified as 'Negro.' Surprisingly, about 56,000 persons took the time to write in under the 'some other race' category the word 'Negro.' Above half of them were less than 45 years of age in 2000.
"The Census Bureau didn't do any research on the respondent reaction to the word 'Negro' in the 2000s, but did do tests that showed answers to the ethnicity and race questions tended to change depending on the order of the questions. I think some research on the sensitivity of answers to the presence of 'Negro' should have been done last decade, but I am unaware of what limitations there were on the research program then."
We asked readers what they thought about it at the time, and it was tight. But about 53 percent of those who answered our question seemed to find it OK.
However, Census Bureau research and public feedback turned up different results, so moving forward "Negro" will not be an option.
Copyright 2021 NPR. To see more, visit https://www.npr.org.


text:
Contact Us
Phone: 0141 225 0430
My Account
Sign-in to your account >
Heating Calculator
Calculate your BTU for each room
Delivery will vary depending on the product, delivery lead times are stated on each individual product listing on our website. When your order is being dispatched we will email you a delivery date notification. Deliveries are generally by courier and take place between 8am and 6pm Monday to Friday.
Please see below our delivery guide:
Heated Towel Rails - Next working day (orders placed before 2pm). Electric rails may take an extra day due to the filling process.
Designer Radiators - Next working day (orders placed before 2pm). Electric radiators may take an extra day due to the filling process.
Convector Radiators - 2-7 working days.
Aluminium Radiators - 2-7 working days.
Curved Bay Radiators - 10 working days, these are 'made to order'.
Column Radiators – 3-4 working days. For custom paint colours delivery is usually 7-10 working days as these are 'made to order'.
Cast Iron Radiators – 5 working days for metallic paint or primer (undercoat). Custom paints and special finishes (Antiqued, Hightlight or Polished) deliver in 10 working days. Cast iron radiators are all 'made to order'.
Valves and Accessories – Next working day (orders placed before 2pm)
Signing For Goods
Once the goods arrive with you, please remember to check that you are signing to certify items arrive in perfect condition. If the packaging looks damaged in any way, please open the item and check it whilst the driver is there to check for damage. If the item is damaged you should refuse the item. If you don't have time to check the parcel, you must sign for the item as 'UNCHECKED'. NOTE: Sorry, we will not accept returns for items that have been damaged by the courier and then signed for as in perfect condition, as we cannot claim for these damages. If in doubt ensure you sign for items as 'UNCHECKED'.
Damages or Missing Items
Please inspect all goods on arrival for any damages, faulty or missing items and notify us of any problems within 3 working days of receipt of your goods. Trade Radiators cannot be held responsible for damaged/missing/faulty items reported after this time as clearly stated in our Terms & Conditions.
Delivery Service
Deliveries are usually made by courier between the hours of 8am and 6pm Monday to Friday. Please note that couriers UK wide are only contracted/insured to deliver kerb/roadside therefore you may have to bring the radiator(s) into your property yourself and for large or heavy items you may require assistance.
Contact Us
Phone: 0141 225 0430
My Account
Sign-in to your account >
Heating Calculator
Calculate your BTU for each room


text:
Joe Gilet Harvard Grey
Joe doesn't do sale. All our Joes are not only timeless classics but are manufactured and sold at fair prices. Still, we can offer you a sweeter deal if you buy more Joes in one go. We cut down on our costs, and you get a discount. It's a win-win, really.
save more
Note: our care products, giftcards and 2-, 3-, and 4-packs: socks, under (fine) and boxershorts are excluded from the Buy More Save More deal.
- Inside the EU: Free shipping and returns
- Return a pullover? No problem! Any time and reason
- In house service center
Color description
Grey boring? Think again.
This bright colour will bring out your complexion and transport you to the Boston campus.
Elitist? We prefer 'exclusive'.
- Material 100% extrafine Merino wool?
- Fineness 19,5 microns ?
- Weight 180 grams ?
- Colour nameHarvard Grey
- ColourGrey
- Model & Size Our model is 1.85 m, weighs 74 kg and wears a medium
Why Merino wool
- Super soft
- Temperature regulating
- Antibacterial
- Moisture wicking
- Colour-fast
- Retains its shape
- UV protection
- Easy to refresh
Delivery and returns
Delivery | Order before 3:00 pm and we'll send out your order that same day
Delivery is free of charge within the EU (view all shipping costs). Once your order leaves our warehouse we will send you a Track & Trace code to track your order and the time of delivery.
- Through the post. For more information check out our returns & exchanges page
- Go to one of our brick and mortar stores in Amsterdam, Leidschendam, Antwerp, Düsseldorf or Cologne.
Size calculator
Uncertain about your size? Based on the experience of our customers, we can thoroughly estimate your size.
Answer below three simple questions and Joe will give you the right advice right away.
John is 1.85 m, weighs 74 kg and wears Medium.
- Style
- Material
- Maintenance
- Reviews
Joe Gilet
Tailored sleeve-less high-button vest. In short: Perfect like Joe.
What to expect
A tailored vest of fine Merino wool. The perfect companion for a blazer jacket but alone it holds up just as well.
True, 100% extra fine Merino wool craves some attention, but in return will last you a long time.100% EXTRA FINE MERINO WOOL
The extra fine Merino wool Joe uses is about 19.5 micron thick. The structure and fineness of our Merino wool are the reasons our Joes feel soft and are not prickly.
Merino wool is praised world wide for its softness, strength, breathability and temperature regulating benefits. In addition, merino wool is 100% natural, renewable and biodegradable. All these beautiful natural properties make merino wool an extremely comfortable fabric to wear. Perfect for all seasons!
Thanks to Merino wool's antibacterial qualities, you don't have to wash your Joe very often. Just air your Joe outside for a night, and he will be ready for wear the next day!
Still, we recommend washing your Joe every now and then. You can do this simply and easily on the wool wash cycle in the washing machine (30° maximum, spin cycle no more than 600 rpm.). Take a look at the maintenance instructions below for best results.
Take care of your Joe
Top Qualität für Merino-Wolle
Tolle Qualität
Sehr gute Qualität
Nur zu empfehlen
Alles wie immer super !
Die Bearbeitung des Produkts war sehr gut.
Alles bestens!
Der Beschenkte hat sich sehr gefreut. Größe genau wie angegeben.


text: This is the contributions page for an IP user, identified by the user's numerical IP address. Some IP addresses change periodically, and may be shared by several users. If you are an IP user, you may create an account or log in to avoid future confusion with other IP users. Registering also hides your IP address. |


text:
Remember The Milk is the smart to-do app for busy people. You'll never forget the milk (or anything else) again.
- Get to-dos out of your head, and let the app remember for you
- Get reminded via email, text, IM, Twitter, and mobile notifications
- Share your lists and give tasks to others to get things done faster
- Stay magically in sync on all of your devices
- Organize the way you want to with priorities, due dates, repeats, lists, tags, and more
- Search your tasks and notes, and save your favorite searches as Smart Lists
- See tasks nearby and plan the best way to get things done
- Integrates with Gmail, Google Calendar, Twitter, Evernote, and more


text:
Orrick, MO Internet Access
Internet Connectivity in Orrick
^ An estimated 573 Orrick residents are connected to the Internet either at home, work, elsewhere or at multiple locations [1].
Internet Availability in Orrick
^ Collectively (all cities), 72.4% of all Missouri residents live in a household where Internet is available, which ranks 37th in the nation [2].
Disconnected in Orrick
^ There are an estimated 265 Orrick residents who are not connected to the Internet at all - whether at home, work, or elsewhere [1].


text:
Breezy Blue Running Socks 1/4 Length
$ 15.95
Steigen Running Socks are designed to feel like you're not wearing socks at all!
In stock
Steigen Running Socks are designed to feel like you're not wearing socks at all!
Athletic or Running Socks are an accessory for comfort – the less you feel them the better.
Steigen running socks are thin which creates minimal space between the shoe and your foot.
This then leads to less movement in the shoe and then less fiction/heat.
Steigen Running Socks are designed to create an environment in which blisters are less likely to form.
They are designed to give the wearer a more responsive feeling from foot and shoe.
- Forefoot pad for comfort and durability
- Arch supports
- Lightweight fabric for fast moisture transfer and breathability
- Microfiber nylon (80%) with Lycra (20%) for form fit
- Airflow top mesh
- Super flat toe seam for superior comfort
- Ankle-crease reduction channels
- Greater control
- 100% Blister Free Guarantee
Steigen Is Made By Athletes, For Athletes.
Additional Information
Brand | Steigen |
Fit | 5 – 12 |
Gender | Men, Unisex, Women |
There are no reviews yet.
Only logged in customers who have purchased this product may leave a review.


text:
Files released so far...
765 / 779
Index pages
WikiLeaks and the Guantánamo Prisoners Released from 2002 to 2004 (Part Four of Ten)
WikiLeaks and the Guantánamo Prisoners Released from 2002 to 2004 (Part Three of Ten)
WikiLeaks and the Guantánamo Prisoners Released from 2002 to 2004 (Part Two of Ten)
WikiLeaks and the Guantánamo Prisoners Released from 2002 to 2004 (Part One of Ten)
The Unknown Prisoners of Guantánamo (Part Five of Five)
The Unknown Prisoners of Guantánamo (Part Four)
WikiLeaks and the 22 Children of Guantánamo
Abandoned in Guantánamo: WikiLeaks Reveals the Yemenis Cleared for Release for Up to Seven Years
The Unknown Prisoners of Guantanamo (Part Three)
The Unknown Prisoners of Guantanamo (Part Two)
Policy Files
By country
Algeria (26/26)
Australia (2/2)
Azerbaijan (1/1)
Bahrain (6/6)
Bangladesh (1/1)
Belgium (2/2)
Canada (1/2)
Chad (1/1)
China (22/22)
Denmark (1/1)
Egypt (5/6)
Ethiopia (1/1)
France (7/7)
Gaza (1/1)
Indonesia (1/1)
Iran (3/3)
Iraq (8/9)
Jordan (7/8)
Kazakhstan (3/3)
Kenya (1/1)
Kuwait (13/13)
Lebanon (1/1)
Libya (11/11)
Malaysia (2/2)
Maldives (1/1)
Mauritania (3/3)
Morocco (13/14)
Pakistan (69/69)
Qatar (1/1)
Russia (9/9)
Saudi Arabia (134/135)
Saudi Arabia/Palestine/Israel (1/1)
Somalia (4/4)
Spain (1/1)
Sudan (11/12)
Sweden (1/1)
Syria (10/10)
Tajikistan (10/12)
Tanzania (1/1)
Tunisia (12/12)
Turkey (5/5)
Uganda (1/1)
United Arab Emirates (2/2)
United Kingdom (9/9)
Uzbekistan (6/6)
West Bank (3/3)
Yemen (3/3)
Yemen (110/110)
Our Partners
The McClatchy Company
El País
The Telegraph
Der Spiegel
Le Monde
La Repubblica
Andy Worthington
Community resources
courage is contagious
The Guantanamo Files
On Sunday April 24, 2011 WikiLeaks began publishing 779 secret files from the notorious Guantanamo Bay prison camp. The details for every detainee will be released daily over the coming month.
Aiat Nasimovich Vahitov
Country | Russia |
Place of birth | Naberyozhnyj, RS |
Birth date | 03/27/77 |
How to Read WikiLeaks' Guantánamo Files ?
The nearly 800 documents in WikiLeaks' latest release of classified US documents are memoranda from Joint Task Force Guantánamo (JTF-GTMO), the combined force in charge of the US "War on Terror" prison at Guantánamo Bay, Cuba, to US Southern Command, in Miami, Florida, regarding the disposition of the prisoners.
Written between 2002 and 2008, the memoranda were all marked as "secret," and their subject was whether to continue holding a prisoner, or whether to recommend his release (described as his "transfer" -- to the custody of his own government, or that of some other government). They were obviously not conclusive in and of themselves, as final decisions about the disposition of prisoners were taken at a higher level, but they are very significant, as they represent not only the opinions of JTF-GTMO, but also the Criminal Investigation Task Force, created by the Department of Defense to conduct interrogations in the "War on Terror," and the BSCTs, the behavioral science teams consisting of psychologists who had a major say in the "exploitation" of prisoners in interrogation.
Under the heading, "JTF-GTMO Detainee Assessment," the memos generally contain nine sections, describing the prisoners as follows, although the earlier examples, especially those dealing with prisoners released -- or recommended for release -- between 2002 and 2004, may have less detailed analyses than the following:
1. Personal information
Each prisoner is identified by name, by aliases, which the US claims to have identified, by place and date of birth, by citizenship, and by Internment Serial Number (ISN). These long lists of numbers and letters -- e.g. US9YM-000027DP -- are used to identify the prisoners in Guantánamo, helping to dehumanize them, as intended, by doing away with their names. The most significant section is the number towards the end, which is generally shortened, so that the example above would be known as ISN 027. In the files, the prisoners are identified by nationality, with 47 countries in total listed alphabetically, from "az" for Afghanistan to "ym" for Yemen.
2. Health
This section describes whether or not the prisoner in question has mental health issues and/or physical health issues. Many are judged to be in good health, but there are some shocking examples of prisoners with severe mental and/or physical problems.
3. JTF-GTMO Assessment
a. Under "Recommendation," the Task Force explains whether a prisoner should continue to be held, or should be released.
b. Under "Executive Summary," the Task Force briefly explains its reasoning, and, in more recent cases, also explains whether the prisoner is a low, medium or high risk as a threat to the US and its allies and as a threat in detention (i.e. based on their behavior in Guantánamo), and also whether they are regarded as of low, medium or high intelligence value.
c. Under "Summary of Changes," the Task Force explains whether there has been any change in the information provided since the last appraisal (generally, the prisoners are appraised on an annual basis).
4. Detainee's Account of Events
Based on the prisoners' own testimony, this section puts together an account of their history, and how they came to be seized, in Afghanistan, Pakistan or elsewhere, based on their own words.
5. Capture Information
This section explains how and where the prisoners were seized, and is followed by a description of their possessions at the time of capture, the date of their transfer to Guantánamo, and, spuriously, "Reasons for Transfer to JTF-GTMO," which lists alleged reasons for the prisoners' transfer, such as knowledge of certain topics for exploitation through interrogation. The reason that this is unconvincing is because, as former interrogator Chris Mackey (a pseudonym) explained in his book The Interrogators, the US high command, based in Camp Doha, Kuwait, stipulated that every prisoner who ended up in US custody had to be transferred to Guantánamo -- and that there were no exceptions; in other words, the "Reasons for transfer" were grafted on afterwards, as an attempt to justify the largely random rounding-up of prisoners.
6. Evaluation of Detainee's Account
In this section, the Task Force analyzes whether or not they find the prisoners' accounts convincing.
7. Detainee Threat
This section is the most significant from the point of view of the supposed intelligence used to justify the detention of prisoners. After "Assessment," which reiterates the conclusion at 3b, the main section, "Reasons for Continued Detention," may, at first glance, look convincing, but it must be stressed that, for the most part, it consists of little more than unreliable statements made by the prisoners' fellow prisoners -- either in Guantánamo, or in secret prisons run by the CIA, where torture and other forms of coercion were widespread, or through more subtle means in Guantánamo, where compliant prisoners who were prepared to make statements about their fellow prisoners were rewarded with better treatment. Some examples are available on the homepage for the release of these documents: http://wikileaks.ch/gitmo/
With this in mind, it should be noted that there are good reasons why Obama administration officials, in the interagency Guantánamo Review Task Force established by the President to review the cases of the 241 prisoners still held in Guantánamo when he took office, concluded that only 36 could be prosecuted.
The final part of this section, "Detainee's Conduct," analyzes in detail how the prisoners have behaved during their imprisonment, with exact figures cited for examples of "Disciplinary Infraction."
8. Detainee Intelligence Value Assessment
After reiterating the intelligence assessment at 3b and recapping on the prisoners' alleged status, this section primarily assesses which areas of intelligence remain to be "exploited," according to the Task Force.
9. EC Status
The final section notes whether or not the prisoner in question is still regarded as an "enemy combatant," based on the findings of the Combatant Status Review Tribunals, held in 2004-05 to ascertain whether, on capture, the prisoners had been correctly labeled as "enemy combatants." Out of 558 cases, just 38 prisoners were assessed as being "no longer enemy combatants," and in some cases, when the result went in the prisoners' favor, the military convened new panels until it got the desired result.


text:
Saturday, February 5, 2011
Homemade Hazelnut Spread - World Nutella Day
From the kitchen of One Perfect Bite...Information about World Nutella Day can be found here.
The last recipe in this week's chocolate extravaganza comes on World Nutella Day. Nutella is the brand name of a sweet hazelnut-based spread made by the same folks who distribute the Ferrero Roche chocolates that are so popular during the holiday season. Their spread is based on gianduja, a sweet chocolate and hazelnut confection that was developed centuries ago in Turin, Italy. Gianduja is used in candy making and to flavor milk and other beverages. Many people use it as they would peanut butter and spread it on bread or toast for snacks. I don't think many would debate how delicious the spread is. There are many who would debate how healthy it is for you. Good or bad, it's here to stay and the lucky folks at Ferrero are probably delighted that their brand name is now generically used to identify most hazelnut spreads available to consumers. That's brand recognition at its best. Gianduja, which contains just four ingredients, is simple to make now that we have food processors and blenders at our disposal. Anyone who has easy access to hazelnuts or filberts can make this in a matter of minutes. I am fortunate to live in the state of Oregon where one of the major export crops is hazelnuts. That means I have a ready and relatively inexpensive source of nuts with which to make the spread. So, sometimes I do. I thought you'd enjoy seeing how it's made. Here's the recipe for the homemade version of Nutella.
Homemade Hazelnut Spread...from the kitchen of One Perfect Bite
2 cups chopped toasted hazelnuts (filberts)
3/4 cup to 1 cup powdered sugar
1/4 cup unsweetened dark cocoa powder
1/8 to 1/4 cup canola oil
Place hazelnuts in the work bowl of a food processor fitted with a metal blade. Process until nuts start to clump together in a ball. This will take some time (about five minutes), so be patient. Add powdered sugar and cocoa powder and process again for 2 to 3 minutes, until mixture turns dark and ingredients are well combined. Now, slowly drizzle in enough oil to make a spread. Store in an airtight container in the refrigerator for 4 to 6 weeks. Yield: 2 cups.
You might also enjoy these recipes:
Nutella Scones - I'll Have What She's Having
Peanut Butter Nutella Cookie Cups - Barbara Bakes
Nutella Crepes - A Little Bit of Everything
Nutella Pop Tarts - Piece of Cake
Nutella Fudge - Annie Bakes
Self-Frosting Nutella Cupcakes - Playing House
French Yogurt Cake with Nutella - Stacey Snacks
112 comments :
- CaThY said...
wow, the recipe is very easy to follow & the Hazelnut spread looks great~ =)
- February 5, 2011 at 12:39 AM
My own homemade hazelnut spread? Yes, please!
- February 5, 2011 at 12:41 AM
- CarinE said...
Nutella is my favorite. Hazelnuts are very expensive here in mu country...I'll make this soon when I have enough money...
- February 5, 2011 at 12:43 AM
- Angie's Recipes said...
Mary, homemade nutella...wow...I am so thrilled to read it from my dashboard...this is an awesome and worth-to-keep recipe!
- February 5, 2011 at 12:45 AM
- Carolyn™ said...
I love hazelnuts and its looks so easy, unfortunately hazel nuts arent cheap here.
- February 5, 2011 at 12:47 AM
- Janet Marie said...
Oh, I don't know...I'm too old to adopt. I think I just want to camp out at your kitchen table and have you feed. :) That works in my mind.
Yummy!!!! {again - :)} - February 5, 2011 at 12:57 AM
- Sanyukta Gour(Bayes) said...
wow...yum n delicious...simply amazing
- February 5, 2011 at 1:14 AM
- tasteofbeirut said...
I have seen many recipes for a Nutella type spread, especially on French blogs, but your recipe strikes me as not too sweet, nutty, and spectacular!
- February 5, 2011 at 1:17 AM
- Sutapa said...
Wow! Mary Love the way you make such an easy homemade hazelnut spread! A keeper!
- February 5, 2011 at 1:34 AM
- Chiara said...
I think Nutella is one of the most fabulous italian product!I love it...your Nutella is really delicious! have a lovely weekend...
- February 5, 2011 at 1:38 AM
- Ginny Hartzler said...
There is actually a special day for Nutella?? This looks very good, and I like Nutella, I have som in the kitchen now. I had no idea you could make it. But how silly of me.
- February 5, 2011 at 1:40 AM
- Alessandra said...
So nice, and this version is also dairy free!
My problem is that I don't need bread... just a spoon
happy world nutella day
Alessandra - February 5, 2011 at 2:11 AM
- Pushpa said...
Homemade Nutella,I have to try this,looks absolutely superb.
- February 5, 2011 at 2:37 AM
- Three-Cookies said...
Good to know for sure. Your version has high hazelnut content and no mystery ingredients! Other day I was in a supermarket, picked up a bottle of choc spread, look at the contents and put it back where it belonged. Hazelnut content was few percentage!
- February 5, 2011 at 3:25 AM
- muppy said...
I would have thought there was more ingredients. So interesting, thanks.
- February 5, 2011 at 3:28 AM
- Unknown said...
wow, so easy and so tasty! well done you for working this one out and thanks for the recipe
- February 5, 2011 at 3:52 AM
- Cherine said...
This is one awesome recipe!! Your homemade nutella looks wonderful!
- February 5, 2011 at 4:31 AM
- Three-Cookies said...
Just after reading your post I saw David Lebovitz's post on nutella. It mentions 'Mary', maybe not you but I had a really good laugh:) http://www.davidlebovitz.com/2011/02/homemade-nutella-recipe-chocolate-hazelnut-spread/
- February 5, 2011 at 4:44 AM
- Terri Steffes said...
Good grief, who knew it was so simple? So, do you have a favorite brand of filberts we should know about?
- February 5, 2011 at 5:00 AM
- Prema said...
Thanks for sharing dear! will try it.
- February 5, 2011 at 5:24 AM
- Love2cook Malaysia said...
Wow...this is soooooooo inviting!!! Home made hazelnut spread..U r rocking! :D
- February 5, 2011 at 5:54 AM
- Red Nomad OZ said...
World Nutella Day???? Who knew such a thing existed!! And who knew how easy this stuff is to make!!
Thanx so much for dropping by my blog on my b-day - always a pleasure to see you!!
Have a great weekend!! - February 5, 2011 at 5:58 AM
- GLENDA CHILDERS said...
Happy Nutella Day. We were first introduced to Nutella in our taking students to Europe days. I rarely buy it . . . but I would sure love to make it.
We are going to be in Cannon Beach in a couple of weeks. I will think of you as my neighbor, while we are there.
Glenda - February 5, 2011 at 6:24 AM
- Big Dude said...
Your chocolate week has been painful to read as I've wanted them all - chocolate is the one sweet I can't resist. Thanks for the Nutella history and recipe.
- February 5, 2011 at 6:41 AM
- Valerie Harrison (bellini) said...
Yum!!!!!!!Just oass me a spoon and I am one happy camper:D:D:D
- February 5, 2011 at 6:50 AM
- Clint said...
Love your chocolate fixation. Keep 'em comin'...
When I first read this recipe, I first thought you said it was based on ganja. I thought, "Oh, boy, this'll be a popular post!"
Blessings. - February 5, 2011 at 6:54 AM
- Caroline B. said...
Hello Mary! A beautiful version of the splendid hazelnut spread. I really like. I took down because I think it is very similar to that of Ferrero Rocher. Have a nice and beautiful day! Caroline B.
- February 5, 2011 at 7:29 AM
- Gloria Baker said...
OMYGOD dear Mary this recipe is absolutely amazing, my kids love Nutella and this look lovely!!! huggs gloria
- February 5, 2011 at 7:38 AM
- Nisrine|Dinners and Dreams said...
I'm curious to see how much better Nutella would taste homemade. It looks silky and delicious for sure!
- February 5, 2011 at 8:01 AM
- Rita said...
got an email from my darling grand daughter last night letting me know it was Nutella day(her favourite thing. I will send her your recipe.
- February 5, 2011 at 8:02 AM
- Noor said...
WOW I bet this is WAY better.
- February 5, 2011 at 8:08 AM
- Jersey Girl Cooks said...
This looks so good! I wonder if another nut could be substituted also? It might be good with walnuts or almonds.
- February 5, 2011 at 8:09 AM
- Carol said...
Your recipe looks easy enough to try at home! Looks delicious, and so creamy!
- February 5, 2011 at 8:23 AM
- Diane said...
I have made a note of this recipe, we have a hazel nut tree which is always laden so this will make a nice change of what to do with them :) Thanks, take care. Diane
- February 5, 2011 at 8:48 AM
- Tanna said...
I had to share this post with my husband. He LOVES nutella, would prefer nuspli, different brand, but cannot find it here. I showed him this recipe and told him he can now make his very own! Thank you. Blessings ~ Tanna
- February 5, 2011 at 8:53 AM
- brokeintrovert said...
I cannot believe this. Wow. Thank you for the recipe...no partially-hygrogenation anywhere.
- February 5, 2011 at 9:02 AM
- CaSaundraLeigh said...
Oh wow, this is great! I've never even thought of making my own "Nutella"! I'll have to make it a point to try this out for sure..thanks!
- February 5, 2011 at 9:07 AM
- Amelia PS said...
i can?t wait to make this! I miss "nocciole" (Italian hazelnuts) very much in the US. Happy Nutella day!
- February 5, 2011 at 9:17 AM
- Brandie@thecountrycook said...
Wow - I had no idea how to make it from scratch! Thank you for sharing this one!
- February 5, 2011 at 9:25 AM
- Christine (Cook the Story) said...
My toddler has never tried nutella because I try to keep foods with palm oil out of the house. The canola oil in this recipe makes it a treat we can all enjoy!
- February 5, 2011 at 9:30 AM
- Lucie said...
I had no idea Oregon exported hazelnuts--good to know! There's nothing better than homemade hazelnut spread on warm fresh bread...perfect!
- February 5, 2011 at 9:32 AM
- Unknown said...
I can not believe I have NEVER tried Nutella! I think it's because I know one spoonful and I wouldn't ever, ever stop! Very cool to see how they make it! Thanks Mary!
- February 5, 2011 at 9:57 AM
Oh wow!! You mean I can make my own Nutella?! Just dangerous! ;)
- February 5, 2011 at 9:59 AM
- Astrid in Bristling Acres said...
Chocolate hazelnut spread is a dangerous thing to have in my house- I'll eat it all up!!!
I started making this last year- I also add a tiny bit of vanilla to my homemade spread. We don't have an excellent supply of hazelnuts (my favorite nut) but we have successfully ordered them from http://www.gnomehazelnutfactory.com/
(and I have absolutely no affiliation with them) - February 5, 2011 at 9:59 AM
- June said...
Mary - I can't believe that's it! The Nutella people are going to be in big trouble now - their sales are dropping as we speak. LOL.
- February 5, 2011 at 10:01 AM
- Angela said...
I had no idea that hazelnuts were an Oregon export. Hmm... you learn something new every day.
- February 5, 2011 at 10:19 AM
- From the Kitchen said...
I've never had Nutella!! Whew, glad to get that off my chest. I love chocolate and hazelnuts (not so abundant and cheap here) and can see how they would be delicious "married" in this way.
Bonnie - February 5, 2011 at 10:21 AM
- Stephen said...
I will have to try this one, since my wife is a Nutella addict.
- February 5, 2011 at 10:22 AM
- Liz That Skinny Chick Can Bake said...
Hi, Mary! What a delicious jar of goodness! So beautiful and decadent! I had to bribe my children to try Nutella this summer...and they were't impressed...can you believe that? I think I could tempt them with your fabulous homemade version, though. Thanks for sharing!
- February 5, 2011 at 10:25 AM
- Pondside said...
The Great Dane wants to celebrate World Nutella Day with a piece of toast with cheese and nutella. He is a fan from waaaaay back and taught the children about the pleasure of this spread many years ago.
Do you know that in Denmark it's quite common to find wafer-thin sheets of chocolate on the breakfast table. I've never been able to adapt to the idea of chocolate on toast, but I can see that it makes lots of people in my family happy! - February 5, 2011 at 10:26 AM
- Harika baratam said...
Nice spread we can use it on bread looks yummy and tempting........
- February 5, 2011 at 10:42 AM
- Kim said...
WOW! What a great recipe Mary... I'll give it a try for sure!
- February 5, 2011 at 10:43 AM
- teresa said...
so yummy! i would never think to make my own hazelnut spread. i bet this is way better then the store bought stuff!
- February 5, 2011 at 10:49 AM
- eatgood4life.blogspot.com said...
I was about to make my own but with peanuts, what a coincidence. I wish I had hazelnuts on hand though. I will try that next time....
- February 5, 2011 at 11:06 AM
- Receitas para a Felicidade said...
Oh Mary Mary Mary what can I do with you? and where they will stop my sugar (diabetes) with these delicious things you made.
Kisses!! - February 5, 2011 at 11:07 AM
- Awayofmind Bakery House said...
Mary, thanks for visiting my blog! It is wonderful to know your blog, the recipes here are lovely, hope you don't mind I create a link to your blog. Have a great weekend!
- February 5, 2011 at 11:09 AM
- Anne said...
Oh mary that is perfection! I love the small ingredient list and can't wait to make this.
- February 5, 2011 at 11:19 AM
- Rhonda said...
My first taste of Nutella was in Paris, I ordered a crepe with chocolate and bananas. It's been true love ever since!
- February 5, 2011 at 11:54 AM
- briarrose said...
So good...what a great, easy recipe. I'm not sure if I could be trusted to whip this up in my kitchen though. The quality control taste tests would take out at least 1/4 of the batch...ehehehe.
- February 5, 2011 at 12:12 PM
- Manzanita said...
A very valuable and nutritious recipe. I make it with cacoa and agave but little differece. Your pictures look so nummy.
Have a marvelous week end.
Love and peace. - February 5, 2011 at 12:35 PM
Happy World Nutella Day! If I had that kind of access to hazelnuts I would probably make this all the time! I love the simplicity of your recipe.
- February 5, 2011 at 12:59 PM
- Sue said...
I have made homemade Nutella also, and I was surprised that it was so easy! Delicious!
- February 5, 2011 at 1:07 PM
- Tammy@Beatrice Banks said...
I did not know these facts. And you can make it homemade? Get out! Sounds wonderful.
- February 5, 2011 at 1:29 PM
- Patricia @ ButterYum said...
Oh Mary - you just made my day. I can't wait to give this recipe a try!
ButterYum - February 5, 2011 at 2:01 PM
- Mrs K said...
One of our friend's sister in India was married to a German,and she introduced us to Nutella in the 90's when nutella in India was an ,"imported product"My daughter had instantly taken to the spread on a toast,I have still not warmed up to that idea and perfer to have mine by the spoon;) Thanks for sharing this decadently yummy recipe,I had no clue it would be this simple.
- February 5, 2011 at 2:32 PM
- Catherine said...
Hi Mary, I just learned that today is World Nutella Day! Well, I love Nutella and have been enjoying it for years! Anyway, I am so impressed that you make your own. Bravo!! Sounds just too good..it would be gone in my house in no time..especially since we are indoors in this long..cold..bleak winter..Blessings to you, Catherine
- February 5, 2011 at 2:38 PM
- Simply Life said...
wow, I can't believe you made your own - this look heavenly!
- February 5, 2011 at 2:52 PM
- Amy I. said...
Hi Mary, thanks for linking to my cupcakes! Your homemade nutella looks divine, it's never occurred to me to make it myself. Happy Nutella Day!
- February 5, 2011 at 2:53 PM
- Chele said...
looks just like the real deal! Can't wait to give this recipe a try ;0)
- February 5, 2011 at 3:16 PM
- Katerina said...
I just made waffles and my son wanted nutella. I wish I had this recipe and make my own, instead of give him store bought.
- February 5, 2011 at 3:29 PM
- Janice said...
That's amazing. I've made my own peanut butter before, but never thought about making Nutella!
- February 5, 2011 at 3:45 PM
- Ana Powell said...
What a lovely swirl.
Well creamy ♥ - February 5, 2011 at 4:37 PM
- Katie@Cozydelicious said...
How could I have missed this who nutella day??? I LOVE nutella! And your version looks just lovely!
- February 5, 2011 at 5:28 PM
- Sheena said...
The nutella looks unbelievably creamy, and I love the simple recipe for it!
- February 5, 2011 at 7:09 PM
- That Girl said...
I've been eating Nutella all week, and I didn't even know about Nutella Day!
- February 5, 2011 at 7:10 PM
- deb said...
What an easy recipe! Adding it to my list to try ♥♥
*hugs*deb - February 5, 2011 at 7:37 PM
- Andrea Riegling from ROCK THAT PLATE! said...
Dang that looks good! I think I'll make it and fill a cake with it!
Anyhoo, I wanted to thank you for all your nice comments! I have added your site to my favorite blogs list on my page! - February 5, 2011 at 8:21 PM
- Unknown said...
I love nutella and enjoyed reading your post. Your homemade version looks amazingly delicious. Thanks for visiting my blog earlier and leaving nice comments. I was honored. I don't know where I have been, but I am so happy to get to know your amazing blog. I am now following.
- February 5, 2011 at 10:10 PM
- Stacey Snacks said...
Hey Mary,
You know how I love that crazy Nutella! Thanks for linking my blog and cake!
Stacey - February 5, 2011 at 10:32 PM
- Elin Chia said...
Mary....your very own homemade hazelnut spread !!! Thanks for sharing the recipe :)
Have a nice day,
Elin - February 5, 2011 at 10:34 PM
- Monet said...
Now I just need to get my hands on some hazelnuts! I love Nutella (who doesn't these days?) but I've never thought of making my own. I love the idea! Thank you for sharing, sweet friend. May your Sunday be one of peace and love.
- February 6, 2011 at 12:00 AM
- Add A Little Love said...
Hey Mary, thanks for visiting my blog and being so kind to leave such nice comment. I followed your link and browsed your blog. You have a wonderful web, and lots of followers. I wonder how you get so many follower on your blog?
Amy - February 6, 2011 at 12:40 AM
- Medeja- CranberryJam said...
I would always prefer such home made spread.. wonderful recipe, Mary :
- February 6, 2011 at 1:40 AM
- Priyanka said...
lovely :)
- February 6, 2011 at 4:20 AM
- Renata said...
I love Nutella and I'd love to try this homemade version. Thanks so much for sharing!
- February 6, 2011 at 5:16 AM
- penny aka jeroxie said...
how ridiculously easy! I have to make some for myself.
- February 6, 2011 at 6:37 AM
- meinekueche said...
is hazelnut can be replace with other nut,such as almonds? so easy to make, but i don't have food processor...humm, must buy food processor first then try this recipe
- February 6, 2011 at 7:07 AM
- Unknown said...
homemade nutella? I bet it is incredible. I have to give this a go. The recipes sounds simple.
Enjoy your Sunday. Michael - February 6, 2011 at 8:58 AM
- Claudia said...
This is the easiest recipe I have found thus far - and I've found a lot. You know how to end a chocolate month!
- February 6, 2011 at 10:21 AM
- A little bit of everything said...
oh my, home made nutella. ii had no idea is so easy to make this delicious and addictive spread. Thanks for sharing the recipe with us Mary. Hope you're having a wonderful Sunday
- February 6, 2011 at 2:37 PM
- Amy at TheSceneFromMe said...
OMG, I love Nutella and it looks fairly easy to make.
I recently found crunchy Nutella in the store and I got so excited!
Yum! - February 6, 2011 at 3:25 PM
- Melissa @IWasBornToCook said...
Looks amazing...something I'll have to try very soon. I'm sure it's delicious!
- February 6, 2011 at 6:29 PM
- ~~louise~~ said...
Now I'm the sorry one Mary. I can't believe I almost missed World Nutella Day & celebrated Chocolate Fondue Day instead.
I am thrilled to know the history behind Nutella. I had no idea. Well you know, I'll be saving this recipe and I will be makin' my own next year!!! In the meantime, I'm adding this link to my post:)
Thanks for sharing... - February 6, 2011 at 8:45 PM
omg!!!! this sounds sooooo yummy!!!!
- February 6, 2011 at 10:42 PM
- Tracy said...
I had no idea you could make homemade hazelnut spread. Mmmm....
- February 6, 2011 at 11:06 PM
- Elaine said...
It's that easy?! I am so glad that I finally broke down and got a food processor a few years ago. I am definitely going to make this. Thank you for sharing the recipe.
- February 6, 2011 at 11:38 PM
- Amanda said...
That looks positively amazing. I have seen this around but haven't tried it yet!
- February 7, 2011 at 9:32 AM
- The Single Nester said...
I first heard of Nutella when visiting my relatives in Italy. They eat it like pb&j. You are really making me drool with all of your great recipes so far this February.
- February 7, 2011 at 5:25 PM
- FOODESSA said...
Just the other day Hubby and I were discussing how turned off we were with the commercial Nutella due to the high sugar content.
He asked me why I didn't make my own. It was a very good question...and now, I have your recipe to inspire me to surprise him.
Thanks Mary ;)
Ciao for now,
Claudia - February 8, 2011 at 8:54 PM
- Megan said...
We all love Nutella and it goes quickly. I really must try your homemade version.
- February 9, 2011 at 9:17 AM
- Pamela said...
HA! I just found your blog (followed the link from FB) and when I saw your header picture, I fell in love. My husband often makes fun of me (in a loving way) that I am the Queen of the perfect bite which is why it takes me so long to eat! I'm gonna have to try this homemade nutella because it does go quickly in our house and must be cheaper than buying it premade! Thanks and looking forward to reading more of your blog!
- March 3, 2011 at 3:46 PM
Looks great. Any sugar substitute you could recommend that would work well?
- March 12, 2011 at 1:37 PM
- Mary Bergfeld said...
Anonymous,I've never tried to make this with a sugar substitute, so I have nothing I can recommend. Sorry. Have a good day. Blessings...Mary
- March 12, 2011 at 2:18 PM
- Robin said...
OMG, thank you for the recipe! I'm a newly converted nutella addict. Got my first jar last week and have been fighting the urge to eat it by the spoonful. I have found that's it's really tasty on graham crackers, and a friend suggested using nutella instead of chocolate to make s'mores.
- March 15, 2011 at 3:08 AM
- Meadowlark said...
Thanks for the recipe and speaking of filberts, you ever try roasting fresh ones over the firepit til they get all smoky flavored and hot. LUSCIOUS!!!! Sadly, we're on the "other side of the mountain" so we have to make these crazy dashes to your side to stock up.
Thx again - June 30, 2011 at 11:23 AM
- Katie said...
I came across this recipe on pinterest.com. I LOVE Nutella! I cannot wait to try this recipe. And it looks so easy!
www.MyMomCareer.com - July 17, 2011 at 4:26 PM
- ...just another preppy shopaholic said...
Awesome, thanks for the recipe!
- August 22, 2011 at 9:31 PM
- amcken3 said...
Is there another oil besides canola that I can use? I found out canola is not healthy. Thank you!
- February 24, 2013 at 11:45 PM
- Unknown said...
great , but my came out lumpy,not smooth. I blended for more them 30 min in the food processor. Could it be because I used hazelnuts with skins, or maybe they won't toasted.
- February 7, 2014 at 2:22 PM
- Mary Bergfeld said...
Evelyn, the nuts should be toasted and skins removed.
- February 7, 2014 at 2:50 PM
- Stacey M. said...
I just made this recipe and here's what I've found.
1. After you toast the hazelnuts, you need to remove as much of the skins as you can by rubbing the nuts vigorously in a clean kitchen towel.
2. You can't process the spread enough in the food processor to get the creamy, non-gritty texture that comes in the jarred version. If that bothers you, you can push the spread through a fine-mesh sieve which will help a lot but it won't be perfect. Its fine by me, but I'm not sure what my kids will think.
3. This is more time and work than it appears, but my be worth it to you if you love the end result.
4. The hazelnut flavor of this spread is much stronger than Nutella. This spread is not very sweet and has more of a stick-to-the-roof-of-your-mouth quality. I also found that the chocolate flavor wasn't very prominent (and I used very high quality cocoa.)
5. This homemade version is well suited to adult tastes that aren't just looking for a sweet hit. It's more complex. That being said, it will never be mistaken for store-bought Nutella.
6. I found that for a flavor and consistency more akin to Nutella, I had to add considerably more powdered sugar, and about 1 1/2 tsp. of vanilla, along with about a 1/4 tsp of salt (which brings out the chocolate flavor more.) I also added a bit more oil for a creamier consistency.
I haven't tried this on my kids yet who are die-hard Nutella fans (and I rarely buy it for them), so we'll see what they say.
Bottom line, I think this is a good Nutella alternative or replacement but not a copycat version.
Enjoy! - May 23, 2014 at 2:08 PM
I have to be honest. This recipe was dreadful. I usually love home made alternatives but this tastes NOTHING like Nutella. This was a waste of expensive hazelnuts and expensive high-quality cocoa. Unfortunately, it's probably the worst recipe I've ever tried. This doesn't taste, look, or feel like Nutella.
- August 2, 2014 at 8:05 PM


text:
Aldo Colombini – Packet Trick Picks
An incredible collection of packet tricks!
PREDICTION GONE WILD (Cameron Francis):A great trick. A card is selected. You show four blank cards with different names of cards on them. All of a sudden all the cards have the name of the selection. At the end the selection vanishes from the deck and appears in the packet.
BOXING ACES (Aldo Colombini):An Ace-assembly that will have their jaws dropping. Four Aces vanish from packets of cards and reappear inside the card case.
GHOST FLIGHT (Peter Duffie):Eight double blank cards and four Queens are used. The Queens trapped between two blank cards vanish and reappear under a ?cover.? Great handling, an incredible effect.
OILS WELL THAT ENDS WELL (Stephen Tucker):A version of the classic ?Oil and Queens? where at the end the four Queens vanish and leave four blank-faced cards.
TRIFLE (Aldo Colombini):Two sets of four-of-a-kind, say Kings, one blue-backed and one red-backed set. One of the four Kings is freely selected by the spectator who announces its suit. The same two Kings change place twice.
KLONDYKE CATO (Richard Vollmer):Amazing simple routine. A spectator shuffles a packet of cards and you reveal how many cards are reversed and the total of their values.
A TRICK FOR JACK PARKER (Paul Gordon):Two packets of red/black cards are used. A card is selected from one packet and it turns out to be the only reversed card. The other cards change into a Royal Flush.
RED BLUES (Karl Fulves):Great packet trick where a card is FREELY selected (say the AH) and it is seen to be the only red-backed card in the packet and the only Ace in the packet.
THE WHITECHAPEL SOLUTION (Ryan Matney):Great patter story about Jack the Ripper where the spectator finally finds the devious killer!
MINDS IN SESSION (Arthur Carter):Great principle to find a different colored card in a packet of seven that can be used for many other routines.
Running TimeApproximately 45min


text:
In the area of Henry's Town Mobli-taa road we have found 0 results for the category Pharmacy. Here are the 0 results which are closest to Henry's Town Mobli-taa road:
Nearby we found in the most important categories for you:
* Unconfirmed addresses: For a few entries in our directory we unfortunately have no confirmation whether the address is correct or not. In these cases, the address is taken from databases or calculated from surrounding places/data. We have indicated these entries in order distinguish them from the rest. If you want to go to one of these addresses, please check your city map or other sources in order to make sure you are on the right way.


text:
Provided by: git-man_2.17.1-1ubuntu0.18_all
git-format-patch - Prepare patches for e-mail submission
git format-patch [-k] [(-o|--output-directory) <dir> | --stdout] [--no-thread | --thread[=<style>]] [(--attach|--inline)[=<boundary>] | --no-attach] [-s | --signoff] [--signature=<signature> | --no-signature] [--signature-file=<file>] [-n | --numbered | -N | --no-numbered] [--start-number <n>] [--numbered-files] [--in-reply-to=Message-Id] [--suffix=.<sfx>] [--ignore-if-in-upstream] [--rfc] [--subject-prefix=Subject-Prefix] [(--reroll-count|-v) <n>] [--to=<email>] [--cc=<email>] [--[no-]cover-letter] [--quiet] [--notes[=<ref>]] [--progress] [<common diff options>] [ <since> | <revision range> ]
Prepare each commit with its patch in one file per commit, formatted to resemble UNIX mailbox format. The output of this command is convenient for e-mail submission or for use with git am. There are two ways to specify which commits to operate on. 1. A single commit, <since>, specifies that the commits leading to the tip of the current branch that are not in the history that leads to the <since> to be output. 2. Generic <revision range> expression (see "SPECIFYING REVISIONS" section in gitrevisions(7)) means the commits in the specified range. The first rule takes precedence in the case of a single <commit>. To apply the second rule, i.e., format everything since the beginning of history up until <commit>, use the --root option: git format-patch --root <commit>. If you want to format only <commit> itself, you can do this with git format-patch -1 <commit>. By default, each output file is numbered sequentially from 1, and uses the first line of the commit message (massaged for pathname safety) as the filename. With the --numbered-files option, the output file names will only be numbers, without the first line of the commit appended. The names of the output files are printed to standard output, unless the --stdout option is specified. If -o is specified, output files are created in <dir>. Otherwise they are created in the current working directory. The default path can be set with the format.outputDirectory configuration option. The -o option takes precedence over format.outputDirectory. To store patches in the current working directory even when format.outputDirectory points elsewhere, use -o .. By default, the subject of a single patch is "[PATCH] " followed by the concatenation of lines from the commit message up to the first blank line (see the DISCUSSION section of git-commit(1)). When multiple patches are output, the subject prefix will instead be "[PATCH n/m] ". To force 1/1 to be added for a single patch, use -n. To omit patch numbers from the subject, use -N. If given --thread, git-format-patch will generate In-Reply-To and References headers to make the second and subsequent patch mails appear as replies to the first mail; this also generates a Message-Id header to reference.
-p, --no-stat Generate plain patches without any diffstats. -U<n>, --unified=<n> Generate diffs with <n> lines of context instead of the usual three. --indent-heuristic Enable the heuristic that shift diff hunk boundaries to make patches easier to read. This is the default. --no-indent-heuristic Disable the indent heuristic. --minimal Spend extra time to make sure the smallest possible diff is produced. --patience Generate a diff using the "patience diff" algorithm. --histogram Generate a diff using the "histogram diff" algorithm. --anchored=<text> Generate a diff using the "anchored diff" algorithm. This option may be specified more than once. If a line exists in both the source and destination, exists only once, and starts with this text, this algorithm attempts to prevent it from appearing as a deletion or addition in the output. It uses the "patience diff" algorithm internally. --diff-algorithm={patience|minimal|histogram|myers} Choose a diff algorithm. The variants are as follows: default, myers The basic greedy diff algorithm. Currently, this is the default. minimal Spend extra time to make sure the smallest possible diff is produced. patience Use "patience diff" algorithm when generating patches. histogram This algorithm extends the patience algorithm to "support low-occurrence common elements". For instance, if you configured diff.algorithm variable to a non-default value and want to use the default one, then you have to use --diff-algorithm=default option. --stat[=<width>[,<name-width>[,<count>]]] Generate a diffstat. By default, as much space as necessary will be used for the filename part, and the rest for the graph part. Maximum width defaults to terminal width, or 80 columns if not connected to a terminal, and can be overridden by <width>. The width of the filename part can be limited by giving another width <name-width> after a comma. The width of the graph part can be limited by using --stat-graph-width=<width> (affects all commands generating a stat graph) or by setting diff.statGraphWidth=<width> (does not affect git format-patch). By giving a third parameter <count>, you can limit the output to the first <count> lines, followed by ... if there are more. These parameters can also be set individually with --stat-width=<width>, --stat-name-width=<name-width> and --stat-count=<count>. --compact-summary Output a condensed summary of extended header information such as file creations or deletions ("new" or "gone", optionally "+l" if it's a symlink) and mode changes ("+x" or "-x" for adding or removing executable bit respectively) in diffstat. The information is put betwen the filename part and the graph part. Implies --stat. --numstat Similar to --stat, but shows number of added and deleted lines in decimal notation and pathname without abbreviation, to make it more machine friendly. For binary files, outputs two - instead of saying 0 0. --shortstat Output only the last line of the --stat format containing total number of modified files, as well as number of added and deleted lines. --dirstat[=<param1,param2,...>] Output the distribution of relative amount of changes for each sub-directory. The behavior of --dirstat can be customized by passing it a comma separated list of parameters. The defaults are controlled by the diff.dirstat configuration variable (see git-config(1)). The following parameters are available: changes Compute the dirstat numbers by counting the lines that have been removed from the source, or added to the destination. This ignores the amount of pure code movements within a file. In other words, rearranging lines in a file is not counted as much as other changes. This is the default behavior when no parameter is given. lines Compute the dirstat numbers by doing the regular line-based diff analysis, and summing the removed/added line counts. (For binary files, count 64-byte chunks instead, since binary files have no natural concept of lines). This is a more expensive --dirstat behavior than the changes behavior, but it does count rearranged lines within a file as much as other changes. The resulting output is consistent with what you get from the other --*stat options. files Compute the dirstat numbers by counting the number of files changed. Each changed file counts equally in the dirstat analysis. This is the computationally cheapest --dirstat behavior, since it does not have to look at the file contents at all. cumulative Count changes in a child directory for the parent directory as well. Note that when using cumulative, the sum of the percentages reported may exceed 100%. The default (non-cumulative) behavior can be specified with the noncumulative parameter. <limit> An integer parameter specifies a cut-off percent (3% by default). Directories contributing less than this percentage of the changes are not shown in the output. Example: The following will count changed files, while ignoring directories with less than 10% of the total amount of changed files, and accumulating child directory counts in the parent directories: --dirstat=files,10,cumulative. --summary Output a condensed summary of extended header information such as creations, renames and mode changes. --no-renames Turn off rename detection, even when the configuration file gives the default to do so. --full-index Instead of the first handful of characters, show the full pre- and post-image blob object names on the "index" line when generating patch format output. --binary In addition to --full-index, output a binary diff that can be applied with git-apply. --abbrev[=<n>] Instead of showing the full 40-byte hexadecimal object name in diff-raw format output and diff-tree header lines, show only a partial prefix. This is independent of the --full-index option above, which controls the diff-patch output format. Non default number of digits can be specified with --abbrev=<n>. -B[<n>][/<m>], --break-rewrites[=[<n>][/<m>]] Break complete rewrite changes into pairs of delete and create. This serves two purposes: It affects the way a change that amounts to a total rewrite of a file not as a series of deletion and insertion mixed together with a very few lines that happen to match textually as the context, but as a single deletion of everything old followed by a single insertion of everything new, and the number m controls this aspect of the -B option (defaults to 60%). -B/70% specifies that less than 30% of the original should remain in the result for Git to consider it a total rewrite (i.e. otherwise the resulting patch will be a series of deletion and insertion mixed together with context lines). When used with -M, a totally-rewritten file is also considered as the source of a rename (usually -M only considers a file that disappeared as the source of a rename), and the number n controls this aspect of the -B option (defaults to 50%). -B20% specifies that a change with addition and deletion compared to 20% or more of the file's size are eligible for being picked up as a possible source of a rename to another file. -M[<n>], --find-renames[=<n>] Detect renames. If n is specified, it is a threshold on the similarity index (i.e. amount of addition/deletions compared to the file's size). For example, -M90% means Git should consider a delete/add pair to be a rename if more than 90% of the file hasn't changed. Without a % sign, the number is to be read as a fraction, with a decimal point before it. I.e., -M5 becomes 0.5, and is thus the same as -M50%. Similarly, -M05 is the same as -M5%. To limit detection to exact renames, use -M100%. The default similarity index is 50%. -C[<n>], --find-copies[=<n>] Detect copies as well as renames. See also --find-copies-harder. If n is specified, it has the same meaning as for -M<n>. --find-copies-harder For performance reasons, by default, -C option finds copies only if the original file of the copy was modified in the same changeset. This flag makes the command inspect unmodified files as candidates for the source of copy. This is a very expensive operation for large projects, so use it with caution. Giving more than one -C option has the same effect. -D, --irreversible-delete Omit the preimage for deletes, i.e. print only the header but not the diff between the preimage and /dev/null. The resulting patch is not meant to be applied with patch or git apply; this is solely for people who want to just concentrate on reviewing the text after the change. In addition, the output obviously lacks enough information to apply such a patch in reverse, even manually, hence the name of the option. When used together with -B, omit also the preimage in the deletion part of a delete/create pair. -l<num> The -M and -C options require O(n^2) processing time where n is the number of potential rename/copy targets. This option prevents rename/copy detection from running if the number of rename/copy targets exceeds the specified number. -O<orderfile> Control the order in which files appear in the output. This overrides the diff.orderFile configuration variable (see git-config(1)). To cancel diff.orderFile, use -O/dev/null. The output order is determined by the order of glob patterns in <orderfile>. All files with pathnames that match the first pattern are output first, all files with pathnames that match the second pattern (but not the first) are output next, and so on. All files with pathnames that do not match any pattern are output last, as if there was an implicit match-all pattern at the end of the file. If multiple pathnames have the same rank (they match the same pattern but no earlier patterns), their output order relative to each other is the normal order. <orderfile> is parsed as follows: • Blank lines are ignored, so they can be used as separators for readability. • Lines starting with a hash ("#") are ignored, so they can be used for comments. Add a backslash ("\") to the beginning of the pattern if it starts with a hash. • Each other line contains a single pattern. Patterns have the same syntax and semantics as patterns used for fnmantch(3) without the FNM_PATHNAME flag, except a pathname also matches a pattern if removing any number of the final pathname components matches the pattern. For example, the pattern "foo*bar" matches "fooasdfbar" and "foo/bar/baz/asdf" but not "foobarx". -a, --text Treat all files as text. --ignore-cr-at-eol Ignore carrige-return at the end of line when doing a comparison. --ignore-space-at-eol Ignore changes in whitespace at EOL. -b, --ignore-space-change Ignore changes in amount of whitespace. This ignores whitespace at line end, and considers all other sequences of one or more whitespace characters to be equivalent. -w, --ignore-all-space Ignore whitespace when comparing lines. This ignores differences even if one line has whitespace where the other line has none. --ignore-blank-lines Ignore changes whose lines are all blank. --inter-hunk-context=<lines> Show the context between diff hunks, up to the specified number of lines, thereby fusing hunks that are close to each other. Defaults to diff.interHunkContext or 0 if the config option is unset. -W, --function-context Show whole surrounding functions of changes. --ext-diff Allow an external diff helper to be executed. If you set an external diff driver with gitattributes(5), you need to use this option with git-log(1) and friends. --no-ext-diff Disallow external diff drivers. --textconv, --no-textconv Allow (or disallow) external text conversion filters to be run when comparing binary files. See gitattributes(5) for details. Because textconv filters are typically a one-way conversion, the resulting diff is suitable for human consumption, but cannot be applied. For this reason, textconv filters are enabled by default only for git- diff(1) and git-log(1), but not for git-format-patch(1) or diff plumbing commands. --ignore-submodules[=<when>] Ignore changes to submodules in the diff generation. <when> can be either "none", "untracked", "dirty" or "all", which is the default. Using "none" will consider the submodule modified when it either contains untracked or modified files or its HEAD differs from the commit recorded in the superproject and can be used to override any settings of the ignore option in git-config(1) or gitmodules(5). When "untracked" is used submodules are not considered dirty when they only contain untracked content (but they are still scanned for modified content). Using "dirty" ignores all changes to the work tree of submodules, only changes to the commits stored in the superproject are shown (this was the behavior until 1.7.0). Using "all" hides all changes to submodules. --src-prefix=<prefix> Show the given source prefix instead of "a/". --dst-prefix=<prefix> Show the given destination prefix instead of "b/". --no-prefix Do not show any source or destination prefix. --line-prefix=<prefix> Prepend an additional prefix to every line of output. --ita-invisible-in-index By default entries added by "git add -N" appear as an existing empty file in "git diff" and a new file in "git diff --cached". This option makes the entry appear as a new file in "git diff" and non-existent in "git diff --cached". This option could be reverted with --ita-visible-in-index. Both options are experimental and could be removed in future. For more detailed explanation on these common options, see also gitdiffcore(7). -<n> Prepare patches from the topmost <n> commits. -o <dir>, --output-directory <dir> Use <dir> to store the resulting files, instead of the current working directory. -n, --numbered Name output in [PATCH n/m] format, even with a single patch. -N, --no-numbered Name output in [PATCH] format. --start-number <n> Start numbering the patches at <n> instead of 1. --numbered-files Output file names will be a simple number sequence without the default first line of the commit appended. -k, --keep-subject Do not strip/add [PATCH] from the first line of the commit log message. -s, --signoff Add Signed-off-by: line to the commit message, using the committer identity of yourself. See the signoff option in git-commit(1) for more information. --stdout Print all commits to the standard output in mbox format, instead of creating a file for each one. --attach[=<boundary>] Create multipart/mixed attachment, the first part of which is the commit message and the patch itself in the second part, with Content-Disposition: attachment. --no-attach Disable the creation of an attachment, overriding the configuration setting. --inline[=<boundary>] Create multipart/mixed attachment, the first part of which is the commit message and the patch itself in the second part, with Content-Disposition: inline. --thread[=<style>], --no-thread Controls addition of In-Reply-To and References headers to make the second and subsequent mails appear as replies to the first. Also controls generation of the Message-Id header to reference. The optional <style> argument can be either shallow or deep. shallow threading makes every mail a reply to the head of the series, where the head is chosen from the cover letter, the --in-reply-to, and the first patch mail, in this order. deep threading makes every mail a reply to the previous one. The default is --no-thread, unless the format.thread configuration is set. If --thread is specified without a style, it defaults to the style specified by format.thread if any, or else shallow. Beware that the default for git send-email is to thread emails itself. If you want git format-patch to take care of threading, you will want to ensure that threading is disabled for git send-email. --in-reply-to=Message-Id Make the first mail (or all the mails with --no-thread) appear as a reply to the given Message-Id, which avoids breaking threads to provide a new patch series. --ignore-if-in-upstream Do not include a patch that matches a commit in <until>..<since>. This will examine all patches reachable from <since> but not from <until> and compare them with the patches being generated, and any patch that matches is ignored. --subject-prefix=<Subject-Prefix> Instead of the standard [PATCH] prefix in the subject line, instead use [<Subject-Prefix>]. This allows for useful naming of a patch series, and can be combined with the --numbered option. --rfc Alias for --subject-prefix="RFC PATCH". RFC means "Request For Comments"; use this when sending an experimental patch for discussion rather than application. -v <n>, --reroll-count=<n> Mark the series as the <n>-th iteration of the topic. The output filenames have v<n> prepended to them, and the subject prefix ("PATCH" by default, but configurable via the --subject-prefix option) has ` v<n>` appended to it. E.g. --reroll-count=4 may produce v4-0001-add-makefile.patch file that has "Subject: [PATCH v4 1/20] Add makefile" in it. --to=<email> Add a To: header to the email headers. This is in addition to any configured headers, and may be used multiple times. The negated form --no-to discards all To: headers added so far (from config or command line). --cc=<email> Add a Cc: header to the email headers. This is in addition to any configured headers, and may be used multiple times. The negated form --no-cc discards all Cc: headers added so far (from config or command line). --from, --from=<ident> Use ident in the From: header of each commit email. If the author ident of the commit is not textually identical to the provided ident, place a From: header in the body of the message with the original author. If no ident is given, use the committer ident. Note that this option is only useful if you are actually sending the emails and want to identify yourself as the sender, but retain the original author (and git am will correctly pick up the in-body header). Note also that git send-email already handles this transformation for you, and this option should not be used if you are feeding the result to git send-email. --add-header=<header> Add an arbitrary header to the email headers. This is in addition to any configured headers, and may be used multiple times. For example, --add-header="Organization: git-foo". The negated form --no-add-header discards all (To:, Cc:, and custom) headers added so far from config or command line. --[no-]cover-letter In addition to the patches, generate a cover letter file containing the branch description, shortlog and the overall diffstat. You can fill in a description in the file before sending it out. --notes[=<ref>] Append the notes (see git-notes(1)) for the commit after the three-dash line. The expected use case of this is to write supporting explanation for the commit that does not belong to the commit log message proper, and include it with the patch submission. While one can simply write these explanations after format-patch has run but before sending, keeping them as Git notes allows them to be maintained between versions of the patch series (but see the discussion of the notes.rewrite configuration options in git-notes(1) to use this workflow). --[no-]signature=<signature> Add a signature to each message produced. Per RFC 3676 the signature is separated from the body by a line with '-- ' on it. If the signature option is omitted the signature defaults to the Git version number. --signature-file=<file> Works just like --signature except the signature is read from a file. --suffix=.<sfx> Instead of using .patch as the suffix for generated filenames, use specified suffix. A common alternative is --suffix=.txt. Leaving this empty will remove the .patch suffix. Note that the leading character does not have to be a dot; for example, you can use --suffix=-patch to get 0001-description-of-my-change-patch. -q, --quiet Do not print the names of the generated files to standard output. --no-binary Do not output contents of changes in binary files, instead display a notice that those files changed. Patches generated using this option cannot be applied properly, but they are still useful for code review. --zero-commit Output an all-zero hash in each patch's From header instead of the hash of the commit. --base=<commit> Record the base tree information to identify the state the patch series applies to. See the BASE TREE INFORMATION section below for details. --root Treat the revision argument as a <revision range>, even if it is just a single commit (that would normally be treated as a <since>). Note that root commits included in the specified range are always formatted as creation patches, independently of this flag. --progress Show progress reports on stderr as patches are generated.
You can specify extra mail header lines to be added to each message, defaults for the subject prefix and file suffix, number patches when outputting more than one patch, add "To" or "Cc:" headers, configure attachments, and sign off patches with configuration variables. [format] headers = "Organization: git-foo\n" subjectPrefix = CHANGE suffix = .txt numbered = auto to = <email> cc = <email> attach [ = mime-boundary-string ] signOff = true coverletter = auto
The patch produced by git format-patch is in UNIX mailbox format, with a fixed "magic" time stamp to indicate that the file is output from format-patch rather than a real mailbox, like so: From 8f72bad1baf19a53459661343e21d6491c3908d3 Mon Sep 17 00:00:00 2001 From: Tony Luck <email@example.com> Date: Tue, 13 Jul 2010 11:42:54 -0700 Subject: [PATCH] =?UTF-8?q?[IA64]=20Put=20ia64=20config=20files=20on=20the=20?= =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig=20diet?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit arch/arm config files were slimmed down using a python script (See commit c2330e286f68f1c408b4aa6515ba49d57f05beae comment) Do the same for ia64 so we can have sleek & trim looking ... Typically it will be placed in a MUA's drafts folder, edited to add timely commentary that should not go in the changelog after the three dashes, and then sent as a message whose body, in our example, starts with "arch/arm config files were...". On the receiving end, readers can save interesting patches in a UNIX mailbox and apply them with git-am(1). When a patch is part of an ongoing discussion, the patch generated by git format-patch can be tweaked to take advantage of the git am --scissors feature. After your response to the discussion comes a line that consists solely of "-- >8 --" (scissors and perforation), followed by the patch with unnecessary header fields removed: ... > So we should do such-and-such. Makes sense to me. How about this patch? -- >8 -- Subject: [IA64] Put ia64 config files on the Uwe Kleine-König diet arch/arm config files were slimmed down using a python script ... When sending a patch this way, most often you are sending your own patch, so in addition to the "From $SHA1 $magic_timestamp" marker you should omit From: and Date: lines from the patch file. The patch title is likely to be different from the subject of the discussion the patch is in response to, so it is likely that you would want to keep the Subject: line, like the example above. Checking for patch corruption Many mailers if not set up properly will corrupt whitespace. Here are two common types of corruption: • Empty context lines that do not have any whitespace. • Non-empty context lines that have one extra whitespace at the beginning. One way to test if your MUA is set up correctly is: • Send the patch to yourself, exactly the way you would, except with To: and Cc: lines that do not contain the list and maintainer address. • Save that patch to a file in UNIX mailbox format. Call it a.patch, say. • Apply it: $ git fetch <project> master:test-apply $ git checkout test-apply $ git reset --hard $ git am a.patch If it does not apply correctly, there can be various reasons. • The patch itself does not apply cleanly. That is bad but does not have much to do with your MUA. You might want to rebase the patch with git-rebase(1) before regenerating it in this case. • The MUA corrupted your patch; "am" would complain that the patch does not apply. Look in the .git/rebase-apply/ subdirectory and see what patch file contains and check for the common corruption patterns mentioned above. • While at it, check the info and final-commit files as well. If what is in final-commit is not exactly what you would want to see in the commit log message, it is very likely that the receiver would end up hand editing the log message when applying your patch. Things like "Hi, this is my first patch.\n" in the patch e-mail should come after the three-dash line that signals the end of the commit message.
Here are some hints on how to successfully submit patches inline using various mailers. GMail GMail does not have any way to turn off line wrapping in the web interface, so it will mangle any emails that you send. You can however use "git send-email" and send your patches through the GMail SMTP server, or use any IMAP email client to connect to the google IMAP server and forward the emails through that. For hints on using git send-email to send your patches through the GMail SMTP server, see the EXAMPLE section of git-send-email(1). For hints on submission using the IMAP interface, see the EXAMPLE section of git-imap- send(1). Thunderbird By default, Thunderbird will both wrap emails as well as flag them as being format=flowed, both of which will make the resulting email unusable by Git. There are three different approaches: use an add-on to turn off line wraps, configure Thunderbird to not mangle patches, or use an external editor to keep Thunderbird from mangling the patches. Approach #1 (add-on) Install the Toggle Word Wrap add-on that is available from https://addons.mozilla.org/thunderbird/addon/toggle-word-wrap/ It adds a menu entry "Enable Word Wrap" in the composer's "Options" menu that you can tick off. Now you can compose the message as you otherwise do (cut + paste, git format-patch | git imap-send, etc), but you have to insert line breaks manually in any text that you type. Approach #2 (configuration) Three steps: 1. Configure your mail server composition as plain text: Edit...Account Settings...Composition & Addressing, uncheck "Compose Messages in HTML". 2. Configure your general composition window to not wrap. In Thunderbird 2: Edit..Preferences..Composition, wrap plain text messages at 0 In Thunderbird 3: Edit..Preferences..Advanced..Config Editor. Search for "mail.wrap_long_lines". Toggle it to make sure it is set to false. Also, search for "mailnews.wraplength" and set the value to 0. 3. Disable the use of format=flowed: Edit..Preferences..Advanced..Config Editor. Search for "mailnews.send_plaintext_flowed". Toggle it to make sure it is set to false. After that is done, you should be able to compose email as you otherwise would (cut + paste, git format-patch | git imap-send, etc), and the patches will not be mangled. Approach #3 (external editor) The following Thunderbird extensions are needed: AboutConfig from http://aboutconfig.mozdev.org/ and External Editor from http://globs.org/articles.php?lng=en&pg=8 1. Prepare the patch as a text file using your method of choice. 2. Before opening a compose window, use Edit→Account Settings to uncheck the "Compose messages in HTML format" setting in the "Composition & Addressing" panel of the account to be used to send the patch. 3. In the main Thunderbird window, before you open the compose window for the patch, use Tools→about:config to set the following to the indicated values: mailnews.send_plaintext_flowed => false mailnews.wraplength => 0 4. Open a compose window and click the external editor icon. 5. In the external editor window, read in the patch file and exit the editor normally. Side note: it may be possible to do step 2 with about:config and the following settings but no one's tried yet. mail.html_compose => false mail.identity.default.compose_html => false mail.identity.id?.compose_html => false There is a script in contrib/thunderbird-patch-inline which can help you include patches with Thunderbird in an easy way. To use it, do the steps above and then use the script as the external editor. KMail This should help you to submit patches inline using KMail. 1. Prepare the patch as a text file. 2. Click on New Mail. 3. Go under "Options" in the Composer window and be sure that "Word wrap" is not set. 4. Use Message → Insert file... and insert the patch. 5. Back in the compose window: add whatever other text you wish to the message, complete the addressing and subject fields, and press send.
The base tree information block is used for maintainers or third party testers to know the exact state the patch series applies to. It consists of the base commit, which is a well-known commit that is part of the stable part of the project history everybody else works off of, and zero or more prerequisite patches, which are well-known patches in flight that is not yet part of the base commit that need to be applied on top of base commit in topological order before the patches can be applied. The base commit is shown as "base-commit: " followed by the 40-hex of the commit object name. A prerequisite patch is shown as "prerequisite-patch-id: " followed by the 40-hex patch id, which can be obtained by passing the patch through the git patch-id --stable command. Imagine that on top of the public commit P, you applied well-known patches X, Y and Z from somebody else, and then built your three-patch series A, B, C, the history would be like: ---P---X---Y---Z---A---B---C With git format-patch --base=P -3 C (or variants thereof, e.g. with --cover-letter or using Z..C instead of -3 C to specify the range), the base tree information block is shown at the end of the first message the command outputs (either the first patch, or the cover letter), like this: base-commit: P prerequisite-patch-id: X prerequisite-patch-id: Y prerequisite-patch-id: Z For non-linear topology, such as ---P---X---A---M---C \ / Y---Z---B You can also use git format-patch --base=P -3 C to generate patches for A, B and C, and the identifiers for P, X, Y, Z are appended at the end of the first message. If set --base=auto in cmdline, it will track base commit automatically, the base commit will be the merge base of tip commit of the remote-tracking branch and revision-range specified in cmdline. For a local branch, you need to track a remote branch by git branch --set-upstream-to before using this option.
• Extract commits between revisions R1 and R2, and apply them on top of the current branch using git am to cherry-pick them: $ git format-patch -k --stdout R1..R2 | git am -3 -k • Extract all commits which are in the current branch but not in the origin branch: $ git format-patch origin For each commit a separate file is created in the current directory. • Extract all commits that lead to origin since the inception of the project: $ git format-patch --root origin • The same as the previous one: $ git format-patch -M -B origin Additionally, it detects and handles renames and complete rewrites intelligently to produce a renaming patch. A renaming patch reduces the amount of text output, and generally makes it easier to review. Note that non-Git "patch" programs won't understand renaming patches, so use it only when you know the recipient uses Git to apply your patch. • Extract three topmost commits from the current branch and format them as e-mailable patches: $ git format-patch -3
git-am(1), git-send-email(1)
Part of the git(1) suite