text stringlengths 1 299k | label stringclasses 4
values | lang stringclasses 2
values |
|---|---|---|
[Razor-users] report and revoke the same message
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I send mail detected by Razor as spam to the spamtrap, which again reports it
as spam. Before I added the procmail rule to revoke (as my real life account)
Bugtraq messages that were flagged as spam, I manually revoked them as the
spamtrap (which keeps the last 32 messages sent to it). Thus the spamtrap
both reported as spam and revoked the same message. What happens to its trust
rating?
Btw, what does "TeS" stand for?
cmeclax
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9U0iD3/k1hdmG9jMRArnxAKCpw8ZpBWFo3+h7Y2mscN4WER6HEwCfauH9
54LgdFZN2QQONm7awjHKN1c=
=yKwF
-----END PGP SIGNATURE-----
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Razor-users mailing list
Razor-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/razor-users
| scam | en |
HELP! Someone has hacked into my account! | toxic | en |
Weird messages received from ==
This one here has got to be, by far, the strangest of these messages yet. But I'll betcha ten to one that it's connected to that previous IP user and that account user before... Anyway, I have removed a lot of the spacing so as not to bloat out the talk page too much.
U r startin to piss me off. The Colectives wont stop vandalizing. We can vandalize anywhere and anytime. If you protect your page, we will wait until you un-protect it. You will half to. Fucker.
Colective own this page and this user
Colective.
Colective
Colective.preceding unsigned comment added by , at
== | toxic | en |
Asiatic Black Bear
Someone keeps removing the Aiatic Black Bear from the animal table.
anonymous | toxic | en |
"
Dunch
Hello Acroterion. I've tried to create a Dunch surnames page, but the title seems to be protected. Yours was the last name in a trail of article deletion records. I have created a page Dunch (surname) which you can verify is bona fide, but the page really should be called Dunch. When I try to move my page to Dunch, I get the message ""You cannot move a page to this location, because the new title has been protected from creation"". Any chance you could move the page for me or unprotect it so I can move it? Cheers — " | toxic | en |
Thanks for reverting the vandalism to the James Weldon Johnson article. It's one that is close to my heart, and it's also always nice to see that not all anonymous editors are vandals! ) If you aren't already registered, you might read this information to learn a little about why registering is worthwhile, although not required. Best wishes, | toxic | en |
Oppose It's Infact the Full Official Name of the Tournament as everyone can see from the Photo Itself and by going to the ICC's Official Website. Just by changing the Names of the Previous articles and by Putting up useless Reasons won't Help. What's Right will be done Right no matter how hard one tries to change it. I request that this Article be Protected as per it's Current Name Immediately to as Much Time Period as Possible. Thank You | toxic | en |
"
Your block
While I understood your block and I admit I violated WP:PA, only because he came to me and starting baiting, does it make sense now according to his user page? He's being more disruptive and I don't think I was in the wrong, despite my colorful language. (mailbox) " | toxic | en |
"
Regarding this file, as it is a screenshot from a copyrighted program, copyright is owned by the studio, not by whoever grabbed it and posted it to castle-fans.org. Therefore the comment in your upload summary, ""It is a free file, to share, rate, comment etc"" is invalid. The file is, and likely always will be, non-free and its use is governed by our non-free content criteria. " | toxic | en |
When you're known as the guy who argues that women shove entire chihuahuas in their vagina because the animal's struggles feel like a vibrator, yeah, people *do* stop taking you seriously. | adult_sexism | en |
"
Please do not vandalize pages, as you did with this edit to César Chávez. If you continue to do so, you will be blocked from editing. '''''' Talk/Cont " | toxic | en |
Her income from cheque and credit card fraud seems to have been only a small part of her total income at that time. | toxic | en |
3RR block
You have been blocked for 24 hours under the three revert rule. If you wish to appeal please contact another administrator or the mailing list. | Talk 23:43, 11 Apr 2005 (UTC) | toxic | en |
Yes but most of the examples you are citing, are giving the key and the opus number, both of these are less well understood by non-musicians. | toxic | en |
canadian regulatory approvals
further to my previous email , competition act canada and investment canada act approvals are currently contemplated as conditions to closing .
we ( ecc ) have provided ubs and its counsel with all information and warranties that they need to convince themselves that no pre - closing approvals are needed in the circumstances ( they only need to make a post - closing notification ) , but it is ultimately their decision , and we have yet to hear back from their counsel , although we don ' t anticipate any problem .
- - - - - original message - - - - -
from : keohane , peter
sent : monday , february 04 , 2002 9 : 06 am
to : kitchen , louise
cc : milnthorp , rob ; lavorato , john ; whalley , greg ; haedicke , mark e .
subject :
the ecc estate has this morning proposed a frankly over - the - top list of human resource , systems , software and services requirements from ubsw canada after closing . milnthorp and i have just had it out with kyle kitagawa and his counsel . we will let you know .
other items that need to be resolved for closing :
1 . need to finalize canadian master agreement - comments provided saturday
2 . need to finalize canadian transitional services - see above
3 . need to finalize canadian office lease arrangements with landlords
4 . need to finalize the list of ff & e to be kept by the estate
5 . need to finalize the ubs ag counterparty / guarantee issue
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
peter c . m . keohane
vice president , assistant general counsel
and secretary
enron canada corp .
phone : ( 403 ) 974 - 6923
fax : ( 403 ) 974 - 6707
e - mail : peter . keohane @ enron . com | scam | en |
"
Wikipedia:Requests for adminship/Krimpet
Good luck! [review] " | toxic | en |
He should have been in BFDI as Ice cube
Same name | toxic | en |
"As a part of the ""Satanism"" agreement, the Reverend was offered another chance at the Sinagogue of Satan article. I'd like to request that the page be unprotected so that he can have a shot. I'm not saying that it should be immune to an AfD or that if it routinely becomes a bad article it should be immune to such processes, but I'd appreciate it if we can give him another go. Thank you. TALK CONTRIBS
" | toxic | en |
"
:::::::Yeah, a couple of my friends and even my brother. Well, some of 'em are, the rest are happy that he's champ, as I am. Well, there's a couple of people who can challenge. Maybe Ted? Nah, too soon. I thought the DX-Legacy feud was over. Am I trippin' out? Yeah, I'll give you that. DX, Cena, Orton, and Big Show are the only ""top"" people, as oppose to SmackDown's people. " | toxic | en |
/home/dude
Hi,
some time now the following messages were haunting me:
automount[11593]: attempting to mount entry /home/dude
It just came to my attention, that only freshrpm benefitting hosts showed this
up. I grepped through the binaries and found referrences to /home/dude.
# grep /home/dude /usr/bin/*
Binary file /usr/bin/aaxine matches
Binary file /usr/bin/gentoo matches
Binary file /usr/bin/gphoto2 matches
Binary file /usr/bin/gtkam matches
...
I am now relaxed again ;), and pass this info on. Probably Matthias Saou
himself is "dude", and some package has hardwired a path in his build
directory. It would be nice to find out which and fix it, but I am using too
many of the freshrpm suite to narrow it down.
Regards, Axel.
--
Axel.Thimm@physik.fu-berlin.de
_______________________________________________
RPM-List mailing list <RPM-List@freshrpms.net>
http://lists.freshrpms.net/mailman/listinfo/rpm-list
| scam | en |
Raquel--loved her in the 1966 SciFi hit, "Fantastic Voyage." | adult_sexism | en |
. Things have gotten so ridiculous that this block is entirely believable | toxic | en |
This may be helpful: | toxic | en |
opportunity to discuss
sally
i feel i already know you having had the benefit of sitting next to brent for
the last few months - but i realise i have been impolite in not organising a
call just to introduce myself and arrange dates for a visit to houston .
additionally brent , shona and i have spent some excellent time on the subject
of internal control enivronment / operational risk / doorstep and i wanted to
agree potential next steps with you .
do you have anytime today / tomorrow ?
regards
mike | scam | en |
TVD
If my article gets deleted, I'm holding you and BD responsible. | toxic | en |
this is why the article was deleted by Phantomsteve. | toxic | en |
I am always cool,thanks, definition is different that insults, I never need to anonymously harass anyone, no one gets posted on my site until they earn it, and I agree that there should be no more issues... yet H woke up from his hibernation and attacked me and now this revved up admin posted this, and I just want to pre-empt issues is all. Some of your followers have a lot of rage issues. Anyway take care of yourself. | toxic | en |
":::::::::: I grant that it's possible that there are some quantum models that work below the Planck length, but I do not know of any. Any refs. you can supply would be appreciated. Again, it is being proposed that the special theory of relativity, a scientific refinement of Isaac Newton's works, holds that at any given point in time an object in motion's length has contracted and is shorter than that object's length when it is at rest. Therefore the special theory of relativity appears to invalidate Zeno's arrow paradox. I am only arguing this with you, Steaphen, because every single word that you write tends to show that Rucker's claim is valid and belongs right where it is in this article.
::::::::::I will not comment on your feelings about my scientific understanding, as I prefer to assume good faith on your part, and any comment I make would work to invalidate that preference.
:::::::::: — Paine (
" | toxic | en |
"
Well that is what I am trying to say - if you are saying that they can be traced back to the Steppes (!), then why limit saying that it originates from Somerset? Just because ""oo ar"" has entered common popular consciousness thanks to the Wurzels, it doesn't mean that the term originated with them. Surely to list the words using specific evidence in the form of the first recorded usage of that word or phrase is the best way, otherwise list the word or phrase ""West country"". It is an archaic publication, but you may be interested in reading (if you havn't already) ""Wilkinson Sherren's The Wessex of Romance (London: Chapman & Hall, 1902)"" - an extract is here: " | toxic | en |
"
No!You can't take logical answers to the angles you put on coexistence in Wikipedia, and you take all such answers as personal attacks. Indeed, by calling them ""vicious"" you have gone OTT to an extent I clearly never have. Before making a complaint, you would be due to itemise to the word everything you find vicious and enable me to answer both (i) the intent in whatever I was saying (ii) how to say the same site-relevant things in a way you won't feel as vicious. Also itemise to the word what ""behaviour"" there has been,that is not covered by my earlier answer that I have had to defend my character against the behaviour started towards me.
If you don't know me outside Wikipedia, you have no basis to say ""It was an accurate description of your activities."" It was irrelevant to Wikipedia, an outside dispute brought in here. " | toxic | en |
I'm very glad to hear that. | toxic | en |
"
deleted part
Wll ryan we are aspie or aspergian. We have a more fundamental right to edit this page than you. it is like a white person telling a black person what civil rights movement is.
Joe Mele
Why so defensive? Please, I'm trying to work with you here. Plus no one has more rights to edit a page then anyone else. Is there something in particular that offends you about it? If so we can try to rework it from a nuetral point of view, but censoring it is not good at all. T | @ | C
Sorry , But see the talk on the autism talk page. All right I will take it down a notch. Joe Mele
Thanks Joe ) T | @ | C
Please move this discussion to a user page for Joe Mele or relevant ip number, thank you.
26 August 2005
Excuse me but where is the love??? I am a little hurt - Joe Mele
It would simply be better to create a userpage and have discussions there. 26 August 2005
Deleting comments on your talk page
I should point out the wikipage wikipedia:Avoiding common mistakes. This page is essentially a list of rules that others expect you to abide by. The second to last rule is relevent to talk pages. While it's not the case that you can never delete material from your user page it is not considered acceptable to do so to new comments. I wouldn't worry too much about undeleting the comments you have already deleted but I would ask respectfully that you refrain from deleting any further comments (especially those critical of yourself). If you continue to delete critical comments on this page you may find that others take offense in which case they may try to get you banned. 10:18, 2 Oct 2004 (UTC)" | toxic | en |
"
No problem. I kept the article on my watchlist, as I had a feeling it might show up again. XMan " | toxic | en |
"
The ordering was made to make it easier to find the places on the map, not because of any progression of civilization. I personally would prefer alphabetical sorting.
For the names of placemarks I prefer the ancient names (since this is an article about ancient sites) with alternative names and modern names given in parentheses.
Which cities in the list have not been located?
I will change ""location uncertain"" to ""inexact coordinates"" to reflect that onlymy coordinates are not exact as I prefer, and not the location of the site as such is uncertain. E.g. Kish is somewhere in the vicinity of the given coordinates but not in the exact spot. But I am continuously refining the coordinates. " | toxic | en |
REDIRECT Talk:Shipwrecked: Battle of the Islands 2008 | toxic | en |
fw : trader presentation - afternoon of thursday feb 7
louise ,
attached is the " disciplines and sanctions " document we discussed . mercy gil to send you the contact list momentarily .
please let me know if i can help .
stephanie
- - - - - original message - - - - -
from : brackett , debbie r .
sent : wednesday , february 06 , 2002 2 : 23 pm
to : mcginnis , stephanie
subject : fw : trader presentation - afternoon of thursday feb 7
- - - - - original message - - - - -
from : wendy . bannerman - clark @ ubsw . com @ enron
sent : wednesday , february 06 , 2002 2 : 02 pm
to : gil , mercy ; brackett , debbie r . ; tammie . j . schoppe @ smop 9063 . stm . swissbank . com ; lisa . feld @ ubs . com
cc : tanya . castell @ ubsw . com
subject : re : trader presentation - afternoon of thursday feb 7
discipline and sanctions policy attached .
bullet points for credit and market risk policy will come later .
w
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ reply separator _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
subject : trader presentation - afternoon of thursday feb 7
author : lisa feld at i - am / o 2 = f / o 3 = newyork / o 4 = ubs - usa
date : 2 / 6 / 02 10 : 01 am
tammie -
can you kindly confirm details of where , when , # of sessions if
greater than one , for this presentation . i understand you are the
person louise had designated to help us coordinate the
presentation / training . it will be a powerpoint presentation that we
need your assistance ensuring can be projected as well ensuring the
traders / business have adequate number of copies of hand out material .
attached is the presentation . hand outs that we require your
assistance in handling is :
- presentation print out
- mercy gil to supply you with a printed list of contact names phone
and cell phones by end of day today
- wendy bannerman clarke to supply the day 1 policy ( even if still a
draft ) as well as the discipline and sanction policy by end of day
today .
tammie - if you can get all the hand outs in 1 pack that would be
great but it is not required .
please speak with debbie brackett if you have any questions , issues ,
etc and we thank you very much in advance for your assistance .
looking forward to meeting you ,
lisa feld
crc americas
- 010 _ 003 . doc
visit our website at http : / / www . ubswarburg . com
this message contains confidential information and is intended only
for the individual named . if you are not the named addressee you
should not disseminate , distribute or copy this e - mail . please
notify the sender immediately by e - mail if you have received this
e - mail by mistake and delete this e - mail from your system .
e - mail transmission cannot be guaranteed to be secure or error - free
as information could be intercepted , corrupted , lost , destroyed ,
arrive late or incomplete , or contain viruses . the sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e - mail transmission . if
verification is required please request a hard - copy version . this
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments . | scam | en |
"
Lists of slums
Hi, I've just come across List of slums in Venezuela, and it looks like you've created a bunch of lists of this type. Apart form sourcing issues, there's a fundamental terminological issue with calling a place a ""slum"", which is pretty negative. ""List of barrios"" (the Venezuelan term) would be fine, but than it would still be in the ""list of slums"" category. This problem must apply in other cases too. I don't know what to suggest. talk " | toxic | en |
How the hell am I vandalizing the 50 Cent page?
I sourced the text with a credible link. Quit calling it nonsense. If you want to add something to my text to give it some perpective then fine. However, don't call it vandalism when I have proof that he said what he said. Just because you don't like it doesn't make it vandalism. | toxic | en |
Who the hell is user:Moulton? That's not me. | toxic | en |
"
Finally. Now that it has been merged, there won't be as much of a debate over the meme because we don't know how it would be included in the new article. We'll have to see what happens, but I expect the debates to calm down for a little bit. ''''''(talk) " | toxic | en |
"==Sandbox==
Don't take the template out of the sandbox. It says ""don't remove"" for a reason. 11:36, 10 Jan 2005 (UTC)
" | toxic | en |
== Russo-Georgian War ==
The Turkish Army neither did fight alongside the Georgians against Russia, nor did supply weapons during armed hostilities. The purchase of weapons does not warrant inclusion of the country of origin of weapons as combatant. If WP lists every country from which armament is bought by the warring party as combatant, then Israel, Ukraine and the Czech Republic would be listed too. Two of the Turkish-language sources are blogs and therefore not reliable. Not one of the sources indicate that the armament was provided in 7-12 August period. Now please revert your edit, since nobody wants to get involved in edit warring and that article has caused enough trouble. | toxic | en |
Dar es Saleem building collapse picture
Hi Mohammad,
For the Dar es Salaam building collapse picture you added you need to give credit for the person who took it. 5:42, 28 April 2013 | toxic | en |
"
How did I violate Arbcom and what personal attacks did I make? 23:32, September 12, 2005 (UTC)" | toxic | en |
Sorry friend who posted info was drunk | toxic | en |
Very interesting news on his participation in EVE Online==
http://www.theverge.com/2012/9/12/3323012/eve-online-sean-smith-libya-attack
EVE Online players may have been the first ones to possibly be aware of his death. 71.231.197.235
== | toxic | en |
Original game
Any one can make an article or include any information about the first madden game? Funny how the images are of 2001 and 2006 (xbox 360) but none for Nes or super nintendo. | toxic | en |
"
On this day, June 26
""1409 - Western Schism: The Catholic church is led into a double schism as Petros Philargos is crowned Pope Alexander V after the Council of Pisa, joining Pope Gregory XII in Rome and Avignon Pope Benedict XIII in Avignon."" Is the redundant use of Avignon necessary? " | toxic | en |
Go back and re-read my numerous comments about that. No, Dodo merely used 'boilerplate' documents, pre-written, as if that was sufficient. It wasn't. I have raised MANY objections since his initial deletorreah, and no, he has not addressed 98%+ of what I said. Hint: Templates, or 'boilerplate' text, is only appropriate if the person who uses it has applied it correctly, and modified it to address case-specific issues. Templates may be the BEGINNING of a good response, but they are rarely the END. 'Dodo' (and most others 'addressing' the issue, to the extent that they 'address' it) pretends that he can point his finger at my posts, but at the same time ignore HIS OWN actions! THat's not surprising: His actions were thoroughly premature, improper, rude, and abusive. Unless you are willing to actually address my specific objections to his actions, your defense of Dodo is no better than 'meat puppetry'. Others have behaved exactly like you, so you're in bad company. | toxic | en |
"
:::::: Thanks for that! Nw wot we shud do now with that article iOS 7 ?? " | toxic | en |
bosnian language in constitution of montenegro
http://www.sllrcg.cg.yu/001-2007.pdf
official page of 'Sluzbeni List Crne Gore'
Article 13: Bosnian (bosanski - босански) - not Bosniac/Bosniak (bošnjački - бошнјачки) | toxic | en |
site status report and qbr
louise :
as a follow up to our conversation early this week , i will have a draft site status report to you on tuesday . what we ' ve done is to take the site option list previously provided to you , and add a status column and a cost basis column . i ' d like to sit down with you and dave duran to go over this , and also other information on ql to make sure my group is on track from your perspective . i could have a qbr package to you by late next week or early the following , depending on when you would like to get together .
i hope you have a good weekend .
regards ,
ben | scam | en |
This is a vandalism account and i have blocked this user. | Talk | toxic | en |
Q: How do i short older women? Yeah you should be buying those put options on women. Their intrinsic value is going to tank from mgtow... | adult_sexism | en |
==Wikipedia's Rules==
This article violates Wikipedia's Neutral Point Of View Policy, probably the most important rule. It does not even meet Wikipedia's requirements or rules, neither does it reflect a global view on the subject in most sections, outdated, not one single negative thing about it, and some other issues. We strongly disagree with the article! And request an immediate edit with fair representation.
:Anyone is able to edit Wikipedia. I'm sure you can understand that this article gets a lot of vandalism, so it is partially protected from new and unregistered users. Once you get a few edits under your belt, you are able to participate as anyone else does. The first step in doing that is obtaining reliable sources. Wikipedia mirrors information provided in reliable sources per this policy. Inserting information that is not covered in a source is considered original research and is forbidden.
:So what parts of the article do you disagree with? Please provide specific passages and the source material that refutes it. Let me know if you have questions. | toxic | en |
Minor League baseball players are under contract with a 'Professional' team, having to be stored in lower class teams, but still 'professional' players with stats. These type of minor league stub can further knowledge of the player by fans in the seats (with Blackberries etc, thus more webhits) or team scouts.
WP:ATHLETE and 'people of notability' doesn't take into account that a 'player' and a 'person' of notability are two different things. A 'person' is vague to define. A 'player' of notability, say a minor league baseball player, does have stats and awards to his name sometimes, and these stubs can add perfectly to what Wikipedia was meant to be in the first place! I have reliable references and always note the stubs accordingly. | toxic | en |
"
Regarding ""Mr John Richards, the Rector of Datchet"", do we need the honorific Mr?
Source said Mr but that was a quote from an older more respectful time. Removal of honorific more appropriate for 2010 talk
In ""quickly became unsafe..."", should the ellipsis be replaced with a colon?
Yes! And the other instance. Another of my tics. talk
The flow here seems rather breathless, and may benefit from additional punctuation: ""...the building of two new road bridges Victoria Bridge slightly upstream and Albert Bridge slightly downstream which both opened in 1851."" talk
Added a couple of commas and a full-stop. talk
It is factually accurate and verifiable.
a (references): b (citations to reliable sources): c (OR):
The oxforddnb.com reference requires a journal subscription. According to WP:Access to sources, this does not ruin the reference, but I am wondering: is there a free source, or a peek preview available online? The article fact is sufficiently supported by the brief quote in the footnote.
It is broad in its coverage.
a (major aspects): b (focused):
It follows the neutral point of view policy.
Fair representation without bias:
It is stable.
No edit wars, etc.:
It is illustrated by images, where possible and appropriate.
a (images are tagged and non-free images have fair use rationales): b (appropriate use with suitable captions):
Extra credit given for having the featured article requirement of alt text. -)
Overall:
Pass/Fail:
When there was a cantilevered section extending out to but not quite touching the Buckinghamshire pier, how large was the gap? An inch? A handspan?
I wish I knew! I'm pretty sure I've found every mention in the reference works at both Windsor and Maidenhead libraries but I'm going down tomorrow to check the quotes so I'll have another search then. talk
How can the bridge be a ""back-door to Windsor Castle"" when the castle is some distance away from the crossing? I can see how it would have been a convenient back door to the grounds, the estate, Home Park.
Back-door is I think direct from a source. Makes sense for me as I understand the context in relation to the distance to London but I can see why a reader not familiar with the topography might think the castle was hard by the ferry - it's actually about half a mile away. I've changed to ""back-way"" talk
Okay, that's my review—I will watch this space for comments and the article for improvements. Nice article, superb images. Too bad there isn't one of the Divided Bridge which shows its idiosyncrasies in greater detail.
Got the note... Please take your time, and forget the ""seven days"" of the template's boilerplate. " | toxic | en |
soory Pal
I don't know who you are. You didn't sign. You need to validate to me what POV push, is cause I bet you have one too! | toxic | en |
Because women are just as bipolar under stress inducing situations as men are. Think vack to your approach anxiety. Sometimes you're gassed af and sometimes you wanna crawl into a corner and die. They probably get the same thing | adult_sexism | en |
"
== Deadlock ==
I think recent attempts at mediating every small iota about this article is pathetic and futile. Everything will end up as ""No consensus"". It is time to recognize that Normal wikipedia mechanisms do not work about this issue. " | toxic | en |
able to do better than that. | toxic | en |
Changed it back to 300 BC because of your weak arguments. | toxic | en |
AK. Get the barcalounger out, old chum. I think you'll be either square-bashing or in solitary on force fart-sack lie-ins wikipedia-wise again! You're right, but might is mightier than being right. When you get back, leave the drivel pages. You've important work to do. | toxic | en |
, 27 January 2013 (UTC)
Minor misread, but understandable. I'm not seeing a frame of reference in the target language (English) where this should be a topic of such rabid coverage; there's no basis in third-party refs in the target language at all. As a matter of fact, there's really nothing readily available in English that the subject himself does not have a hand in directly, and I'm still not seeing how this meets AUTHOR. Reliable sources in any language are fine, but we've got a lot more content here than in ro-wp, where there is (or should be) a lot more coverage. Tudor's article bears that out - there are lots of book references there in multiple languages, and I'm not seeing that here, even minimally. 04:44 | toxic | en |
Tata Steel
Please stop. If you continue to vandalize pages, you will be blocked from editing Wikipedia. | toxic | en |
"
MLK incident
It's true that Greenberg said what he said. It's true that a Chicago Sun Times blog reported what he said. Those two facts, in and of themselves, do not make the MLK incident ""relevant"" to his ESPN career. The fact that there was no meaningful followup coverage in reliable sources should establish that. Alleging that Greenberg's comment was a Freudian slip simply because he has mentioned making such slips requires a citation from a reputable source establishing that he said he makes Freudian slips. I'll assume good faith on the part of the IP editor who has been reinserting the MLK incident, but I strongly question the relevance of including what appears to be a simple spoonerism, even if it has racial connotations. " | toxic | en |
If McCabe is endeavoring to "Fuck Trump" whether literally or figuratively, it violates his oath to uphold the U.S. Constitution. Do cuck's words matter (his wife is paid by people's enemy)? [URL] | adult_sexism | en |
I am not inclined to consider flipping. But I'll ask again right now if someone would please tell us whether the subject of the BLP expressed to Jimbo Wales a general preference about how she wants to be publicly known, versus a mere preference about how this Wikipedia article should be named. I have asked twice at Jimbo's talk page twice. As things stand, I would just go with what reliable sources say about prevalent use, and with what reliable sources say about her own use of her name, which together strongly support the move. | toxic | en |
We should add dates instead of «currently». What is currently? We update thses pages once a week, sometimes months! | toxic | en |
Merger_proposal
Nintendo Ultra 64 Sound Format could be merged into this format, given the discussion at the AfD and DRV. The primary reliable source provided (ieee) notes USF only in passing with regard to PSF. Thoughts? | toxic | en |
:See also . Given that all the major secondary sources (FNA, Tropicos, TPL and WCSP) don't recognize this species, there's no case for doing so here. | toxic | en |
==Reorganize the ship list?==
I'd like to propose reorganizing the listing of Cunard ships the way it is done in the White Star Line entry, where it is listed by date, and includes all the ships. I'm launching (pun intended) a project to write entries for all the White Star ships, and would like to follow up with all the Cunard ships. Would anyone object to me reorganizing the list? | toxic | en |
"
Really , it should be obvious to you from context that I was implying that you were an unpaid or underpaid intern rather than a millionaire working directly for the Clintons. Admit it or not it really is surprisingly popular for political campaigns to hire sub-par, unofficial wikipedians in residence to try and out edit wikipedians that encourage a neutral view of their candidate. I don't know that I agree with all of edits but after and company teaming up to attack a single plea for citation I find it much easier to believe the Professor's good faith. ☎ " | toxic | en |
Afghanistan
Under Afghanistan, it says teh only white people are the pashtuns and the nuristanis. Although both of those people are white, there are others, such as the tajiks( afghan persians), and the pashai | toxic | en |
I am thinking of a darker theme. Does anyone object? | toxic | en |
Please give me a second chance and unblock me. Thank you. | toxic | en |
re : firm power sale from phase i - issues
vince / vasant ,
it has been some time since we spoke at the san antonio conference .
unfortunately , as soon as i got to india i was diagnosed wih a slip disc and
had to be in bed for a long time .
in the mean time the team continued to work on the concept of a sale to
another state out of the dabhol plant . i have developed the concept whereby
we are now looking at a firm component ( over peak period ) , and an infirm
power sale during the monsoon .
the series of quesions and comments from my team in te attachment below
should help you a bit to get a feel for the proposal . i am currently in
houston and reachable at 281 - 345 - 9870 . i maybe needing a surgery for the
slip disc but am currently on medication hoping that surgery won ' t be needed .
i would like to wis you all a very happy x ' mas and a great new year , and will
catch you in the new year in houston to discuss this wit you further . i can
see that soem structuring help will be needed on this , and would like to get
some help from your end .
regards ,
sandeep .
- - - - - - - - - - - - - - - - - - - - - - forwarded by sandeep kohli / enron _ development on
12 / 25 / 99 10 : 17 pm - - - - - - - - - - - - - - - - - - - - - - - - - - -
sandeep kohli
12 / 25 / 99 10 : 06 pm
to : rajesh sivaraman / enron _ development
cc : vivek kejriwal / enron _ development @ enron _ development , shubh
shrivastava / enron _ development @ enron _ development , anshuman
subject : re : firm power sale from phase i - issues
team ,
please find my comments in the word document attached .
please go through this and run the sensitivities and get a good idea of way
to structure thsi . having gone through the comments , i feel that it maybe
necessary to get some help on the structuring side . i will try to get you
some structuring expertise asap . in the mean time , i would like you all to
focus on getting resources together and working this to the next pass .
lets see where we can get with this .
regards ,
sandeep .
rajesh sivaraman
12 / 24 / 99 10 : 06 pm
to : sandeep kohli / enron _ development @ enron _ development
cc : vivek kejriwal / enron _ development @ enron _ development , shubh
shrivastava / enron _ development @ enron _ development , anshuman
subject : firm power sale from phase i - issues
as discussed , please find enclosed a word document which essentially
discusses most of the issues involved with a firm power sale of 50 mw from
phase i , which would have to be sorted out with mseb .
vivek
will put the tariff formula in the next mail )
the tariff structure & the issue list obviously need further refinement ,
before we discuss it with mseb .
looking forward to your comments on both the issue list as well as the tariff
computation .
regards ,
rajesh s | scam | en |
"
Ethnocentric statement of ""discovery"" of gold
How can you discovery something the existence of which has already been established although those that proclaim it discovered were mistaken. Gold was found in California w/early explorers along Colorado River & near Mexican era Los Angeles in 1832 so existence of gold only confirmed not discovered in 1848 although the find was reason for the 1849 Rush, the latter the unique part of incident. To say that gold was discovered in California in 1848 is an ethnocentric statement as well as an example of ignorance by those that either do not want to acknowledge that gold had already been verified as being in California therefore it cannot be a discovery. Finding more gold is not a discovery but a re-confirmation of the existence of gold in the area.66.74.176.59 " | toxic | en |
Uh huh! She shouldâve had it stripped after Benghazi | adult_sexism | en |
":::We'll have to agree to disagree (BTW AE's instructor's name is Neta Snook, not ""Anita""). This article is about Snook, part of which is Snook's frustrations with trying to create safe pilots where there are none. Some editors are leaning in the direction of whitewashing some of the training issues, and doing just that is contrary to traditional aviation training practices. The fact that some editors beat an argument to death doesn't mean that the issue has gone away. As long as there's aviation instructors reading this material, the issue still has legs, regardless of whether you think you've heard enough about it. I know it's a delicate subject, but the successful pilots are those who have never crashed a plane, and never become lost. Snook's job was to train such pilots. This article is still a delicate whitewash of one flight instructor's important mission and is totally unsatisfactory for just that reason.
" | toxic | en |
"
:It sounds like you just resolved the problem. I invite anyone who continues to remove the description to explain why. " | toxic | en |
== homework (again) ==
Ian Suzuki
Mrs. Kovar
Scholarship English 12
13 October 2008
Stranger in a Strange Land Book Summary
Stranger in a Strange Land, written by Robert Heinlein and published in 1961, is widely regarded today as one of the pinnacles of modern science fiction. Many of the ideas and styles that the book introduced in the mid-sixties still resonate with the public’s imagination, prompting some individuals to start actual religions based on the book itself.
Ultimately, the book is centered around Michael Smith, a human orphaned on the surface of Mars as an infant. There, he was immersed from birth into the Martian culture until the age of 20, when a second spaceship came to Mars and recovered Michael. This much is explained in a flashback during the book; the plot of the story begins when Mike is brought back from Mars and tossed into the strange culture of a strange land. The man from Mars takes a while to learn the language, and finds it lacking; his native Martian contains the complexity to express his true feelings.
In particular, the word grok is difficult for Mike to explain, and as he struggles to define this word in English, it becomes apparent that he has powers unexplainable by modern physics or medicine. | toxic | en |
It was just pointed out (and I checked it in Guralnik's Careless Whisper)that Presley did indeed die whilst on the toilet. If you feel it's important then add away. | toxic | en |
re : interim master terms agreement
attached hereto are marked and clean copies of a further revised version of the interim master terms agreement ( financial ) . the changes related primarily to the adoption of guaranty . please call if you have any questions or comments . thanks , anne | scam | en |
. I will do some work on filling in the gaps in the history and evolution of the water treatment speding problems in the province of Ontario. You guys sure know how to write good looking articles | toxic | en |
== Beatlemania ==
JH supplies a drummer to The Beatles!! | toxic | en |
brent darft letter
sally
here is a rough cut draft for you to expand and revise . please use as a
template to include whatever language is
appropriate . after the draft is complete i would run it by rick to see if
there is anything he would add . i hope
the meeting with shankman went well .
tom | scam | en |
Why does Wankopedia continue to support this Debunking Feminized Tool.
you gave up NPOV the day Larry left.. | toxic | en |
More anti white vitriol from a person who is in a position of trust. And she is factually incorrect, black males are by far the most murderous group in society. [URL] | adult_sexism | en |
Category:National Lacrosse League venues
:Category:National Lacrosse League venues, which you created, has been nominated for possible deletion, merging, or renaming. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the Categories for discussion page. Thank you. | toxic | en |
Let me know!
Please let me know, that why you went so harsh and passed negatives comments upon me, while disussing the deletion of Salim Saifullah Khan?
Please let me know! | toxic | en |
Keeping up with The Sims: Managing Large Scale Game Content
URL: http://www.newsisfree.com/click/-0,8613666,159/
Date: 2002-10-06T18:12:54+01:00
With project budgets in the multiple millions of dollars and virtually no
margin for error, more and more development teams are under tremendous pressure
to come out on top of the entertainment software market's cutthroat
competition. No team manager wants to contemplate dropping the ball when
creating the vivid graphics necessary to help make a game a success. Electronic
Arts' The Sims franchise is an excellent example of this pressurized situation.
This article highlights the critical issues that govern the high volume asset
production needed for today's most demanding games.
| scam | en |
"
Looks great to me; you've done nothing wrong here. (talk • contribs) " | toxic | en |
help
Do you enjoy screwing your dog on a regular basis? Or is it just a special occasion thing......
You pick corn out of your feces so you can eat it again too, I suppose. | toxic | en |
"
== Goats ==
From personal experience I can tell you that ""Herding a goat is much harder than herding sheep.[citation needed]"". Sheep are stupid and stick together It is a fact, Goats are crafty buggers that will work out ways to avoid the care of the Goatherd, doing things like suddenly climbing up an unassailable walls or running off suddenly further afield for (goat) goodies en masse but by multiple routes. Tricky bastards. I know its is hardly verifiable, but still, if you have to look afer goats take it as read that ""Herding a goat is much harder than herding sheep."" That is why you have Sheep dog but not Goat dog " | toxic | en |
Deleted page
Here you go: )(Talk) | toxic | en |
Thank you for your kind offer Reinyday. I accept. Admittedly I am very new to Wikipedia and am learning as I go. In my opinion, this will eventually become the most comprehensive and definitive Sweetest Day article anywhere. Contrary to what many may think, I am not anti-Sweetest Day. I simply believe Americans have a right to know the real history of what they are celebrating when it comes to holidays. The Herbert Birch Kingston Story of the origins of Sweetest Day is a verisimilitude, meaning it is very similar to the truth but not the exact truth at all. In fact, the dissemination of this story by Hallmark, American Greetings, Retail Confectioners International and countless other promoters of Sweetest Day is a form of mass deception and market manipulation. It has been going on for 85 years and has resulted in billions of dollars in revenues for these companies. But at what cost? America pays the cost of Sweetest Day in credibility, a trend which must be reversed if we are ever to win the hearts and minds of the world again.
Please allow all images to remain in the article (unless they do not comply with Wikipedia standards). More will be uploaded soon! Also, please do not add any of the verisimilitudes currently used in the promotion of Sweetest Day unless they are characterized as such. Thank you again Reinyday! Robb | toxic | en |
[unison-announce] New unison beta-release (2.9.20) now available
------------------------ Yahoo! Groups Sponsor ---------------------~-->
4 DVDs Free +s&p Join Now
http://us.click.yahoo.com/pt6YBB/NXiEAA/Ey.GAA/26EolB/TM
---------------------------------------------------------------------~->
A new version of unison is now available for testing. It incorporates
several small improvements over 2.9.1, but the main change is a fix to
a bug that had potentially serious safety consequences, but only for
the very small number of users that are in the habit of running more
than one instance of Unison at a time, in parallel. These users are
strongly encouraged to upgrade. Others can wait if they wish.
The release includes pre-built executables for Linux and Solaris, but
not Windows. (We are looking for a Unison-Windows maintainer -- at
the moment, none of the active developers are regularly using Unison
on Windows, and we do not have a machine that is configured properly
for building executables for export.)
Grab it from here:
http://www.cis.upenn.edu/~bcpierce/unison/download.html
Enjoy,
-- Benjamin
Changes since 2.9.1:
* Added a preference maxthreads that can be used to limit the number
of simultaneous file transfers.
* Added a backupdir preference, which controls where backup files
are stored.
* Basic support added for OSX. In particular, Unison now recognizes
when one of the hosts being synchronized is running OSX and
switches to a case-insensitive treatment of filenames (i.e., 'foo'
and 'FOO' are considered to be the same file). (OSX is not yet
fully working, however: in particular, files with resource forks
will not be synchronized correctly.)
* The same hash used to form the archive name is now also added to
the names of the temp files created during file transfer. The
reason for this is that, during update detection, we are going to
silently delete any old temp files that we find along the way, and
we want to prevent ourselves from deleting temp files belonging to
other instances of Unison that may be running in parallel, e.g.
synchronizing with a different host. Thanks to Ruslan Ermilov for
this suggestion.
* Several small user interface improvements
* Documentation
+ FAQ and bug reporting instructions have been split out as
separate HTML pages, accessible directly from the unison web
page.
+ Additions to FAQ, in particular suggestions about performance
tuning.
* Makefile
+ Makefile.OCaml now sets UISTYLE=text or UISTYLE=gtk
automatically, depending on whether it finds lablgtk
installed
+ Unison should now compile ``out of the box'' under OSX
Changes since 2.8.1:
* Changing profile works again under Windows
* File movement optimization: Unison now tries to use local copy
instead of transfer for moved or copied files. It is controled by
a boolean option ``xferbycopying''.
* Network statistics window (transfer rate, amount of data
transferred). [NB: not available in Windows-Cygwin version.]
* symlinks work under the cygwin version (which is dynamically
linked).
* Fixed potential deadlock when synchronizing between Windows and
Unix
* Small improvements:
+ If neither the
tt USERPROFILE nor the
tt HOME environment variables are set, then Unison will put
its temporary commit log (called
tt DANGER.README) into the directory named by the
tt UNISON environment variable, if any; otherwise it will use
tt C:.
+ alternative set of values for fastcheck: yes = true; no =
false; default = auto.
+ -silent implies -contactquietly
* Source code:
+ Code reorganization and tidying. (Started breaking up some of
the basic utility modules so that the non-unison-specific
stuff can be made available for other projects.)
+ several Makefile and docs changes (for release);
+ further comments in ``update.ml'';
+ connection information is not stored in global variables
anymore.
Changes since 2.7.78:
* Small bugfix to textual user interface under Unix (to avoid
leaving the terminal in a bad state where it would not echo inputs
after Unison exited).
Changes since 2.7.39:
* Improvements to the main web page (stable and beta version docs
are now both accessible).
* User manual revised.
* Added some new preferences:
+ ``sshcmd'' and ``rshcmd'' for specifying paths to ssh and rsh
programs.
+ ``contactquietly'' for suppressing the ``contacting server''
message during Unison startup (under the graphical UI).
* Bug fixes:
+ Fixed small bug in UI that neglected to change the displayed
column headers if loading a new profile caused the roots to
change.
+ Fixed a bug that would put the text UI into an infinite loop
if it encountered a conflict when run in batch mode.
+ Added some code to try to fix the display of non-Ascii
characters in filenames on Windows systems in the GTK UI.
(This code is currently untested---if you're one of the
people that had reported problems with display of non-ascii
filenames, we'd appreciate knowing if this actually fixes
things.)
+ `-prefer/-force newer' works properly now. (The bug was
reported by Sebastian Urbaniak and Sean Fulton.)
* User interface and Unison behavior:
+ Renamed `Proceed' to `Go' in the graphical UI.
+ Added exit status for the textual user interface.
+ Paths that are not synchronized because of conflicts or
errors during update detection are now noted in the log file.
+ [END] messages in log now use a briefer format
+ Changed the text UI startup sequence so that
tt ./unison -ui text will use the default profile instead of
failing.
+ Made some improvements to the error messages.
+ Added some debugging messages to remote.ml.
Changes since 2.7.7:
* Incorporated, once again, a multi-threaded transport sub-system.
It transfers several files at the same time, thereby making much
more effective use of available network bandwidth. Unlike the
earlier attempt, this time we do not rely on the native thread
library of OCaml. Instead, we implement a light-weight,
non-preemptive multi-thread library in OCaml directly. This
version appears stable.
Some adjustments to unison are made to accommodate the
multi-threaded version. These include, in particular, changes to
the user interface and logging, for example:
+ Two log entries for each transferring task, one for the
beginning, one for the end.
+ Suppressed warning messages against removing temp files left
by a previous unison run, because warning does not work
nicely under multi-threading. The temp file names are made
less likely to coincide with the name of a file created by
the user. They take the form
.#<filename>.<serial>.unison.tmp.
* Added a new command to the GTK user interface: pressing 'f' causes
Unison to start a new update detection phase, using as paths just
those paths that have been detected as changed and not yet marked
as successfully completed. Use this command to quickly restart
Unison on just the set of paths still needing attention after a
previous run.
* Made the ignorecase preference user-visible, and changed the
initialization code so that it can be manually set to true, even
if neither host is running Windows. (This may be useful, e.g.,
when using Unison running on a Unix system with a FAT volume
mounted.)
* Small improvements and bug fixes:
+ Errors in preference files now generate fatal errors rather
than warnings at startup time. (I.e., you can't go on from
them.) Also, we fixed a bug that was preventing these
warnings from appearing in the text UI, so some users who
have been running (unsuspectingly) with garbage in their
prefs files may now get error reports.
+ Error reporting for preference files now provides file name
and line number.
+ More intelligible message in the case of identical change to
the same files: ``Nothing to do: replicas have been changed
only in identical ways since last sync.''
+ Files with prefix '.#' excluded when scanning for preference
files.
+ Rsync instructions are send directly instead of first
marshaled.
+ Won't try forever to get the fingerprint of a continuously
changing file: unison will give up after certain number of
retries.
+ Other bug fixes, including the one reported by Peter Selinger
(force=older preference not working).
* Compilation:
+ Upgraded to the new OCaml 3.04 compiler, with the LablGtk
1.2.3 library (patched version used for compiling under
Windows).
+ Added the option to compile unison on the Windows platform
with Cygwin GNU C compiler. This option only supports
building dynamically linked unison executables.
Changes since 2.7.4:
* Fixed a silly (but debilitating) bug in the client startup
sequence.
Changes since 2.7.1:
* Added addprefsto preference, which (when set) controls which
preference file new preferences (e.g. new ignore patterns) are
added to.
* Bug fix: read the initial connection header one byte at a time, so
that we don't block if the header is shorter than expected. (This
bug did not affect normal operation --- it just made it hard to
tell when you were trying to use Unison incorrectly with an old
version of the server, since it would hang instead of giving an
error message.)
Changes since 2.6.59:
* Changed fastcheck from a boolean to a string preference. Its legal
values are yes (for a fast check), no (for a safe check), or
default (for a fast check---which also happens to be safe---when
running on Unix and a safe check when on Windows). The default is
default.
* Several preferences have been renamed for consistency. All
preference names are now spelled out in lowercase. For backward
compatibility, the old names still work, but they are not
mentioned in the manual any more.
* The temp files created by the 'diff' and 'merge' commands are now
named by prepending a new prefix to the file name, rather than
appending a suffix. This should avoid confusing diff/merge
programs that depend on the suffix to guess the type of the file
contents.
* We now set the keepalive option on the server socket, to make sure
that the server times out if the communication link is
unexpectedly broken.
* Bug fixes:
+ When updating small files, Unison now closes the destination
file.
+ File permissions are properly updated when the file is behind
a followed link.
+ Several other small fixes.
Changes since 2.6.38:
* Major Windows performance improvement!
We've added a preference fastcheck that makes Unison look only at
a file's creation time and last-modified time to check whether it
has changed. This should result in a huge speedup when checking
for updates in large replicas.
When this switch is set, Unison will use file creation times as
'pseudo inode numbers' when scanning Windows replicas for updates,
instead of reading the full contents of every file. This may cause
Unison to miss propagating an update if the create time,
modification time, and length of the file are all unchanged by the
update (this is not easy to achieve, but it can be done). However,
Unison will never overwrite such an update with a change from the
other replica, since it always does a safe check for updates just
before propagating a change. Thus, it is reasonable to use this
switch most of the time and occasionally run Unison once with
fastcheck set to false, if you are worried that Unison may have
overlooked an update.
Warning: This change is has not yet been thoroughly field-tested.
If you set the fastcheck preference, pay careful attention to what
Unison is doing.
* New functionality: centralized backups and merging
+ This version incorporates two pieces of major new
functionality, implemented by Sylvain Roy during a summer
internship at Penn: a centralized backup facility that keeps
a full backup of (selected files in) each replica, and a
merging feature that allows Unison to invoke an external
file-merging tool to resolve conflicting changes to
individual files.
+ Centralized backups:
o Unison now maintains full backups of the
last-synchronized versions of (some of) the files in
each replica; these function both as backups in the
usual sense and as the ``common version'' when invoking
external merge programs.
o The backed up files are stored in a directory
/.unison/backup on each host. (The name of this
directory can be changed by setting the environment
variable UNISONBACKUPDIR.)
o The predicate backup controls which files are actually
backed up: giving the preference 'backup = Path *'
causes backing up of all files.
o Files are added to the backup directory whenever unison
updates its archive. This means that
# When unison reconstructs its archive from scratch
(e.g., because of an upgrade, or because the
archive files have been manually deleted), all
files will be backed up.
# Otherwise, each file will be backed up the first
time unison propagates an update for it.
o The preference backupversions controls how many previous
versions of each file are kept. The default is 2 (i.e.,
the last synchronized version plus one backup).
o For backward compatibility, the backups preference is
also still supported, but backup is now preferred.
o It is OK to manually delete files from the backup
directory (or to throw away the directory itself).
Before unison uses any of these files for anything
important, it checks that its fingerprint matches the
one that it expects.
+ Merging:
o Both user interfaces offer a new 'merge' command,
invoked by pressing 'm' (with a changed file selected).
o The actual merging is performed by an external program.
The preferences merge and merge2 control how this
program is invoked. If a backup exists for this file
(see the backup preference), then the merge preference
is used for this purpose; otherwise merge2 is used. In
both cases, the value of the preference should be a
string representing the command that should be passed to
a shell to invoke the merge program. Within this string,
the special substrings CURRENT1, CURRENT2, NEW, and OLD
may appear at any point. Unison will substitute these as
follows before invoking the command:
# CURRENT1 is replaced by the name of the local copy
of the file;
# CURRENT2 is replaced by the name of a temporary
file, into which the contents of the remote copy of
the file have been transferred by Unison prior to
performing the merge;
# NEW is replaced by the name of a temporary file
that Unison expects to be written by the merge
program when it finishes, giving the desired new
contents of the file; and
# OLD is replaced by the name of the backed up copy
of the original version of the file (i.e., its
state at the end of the last successful run of
Unison), if one exists (applies only to merge, not
merge2).
For example, on Unix systems setting the merge
preference to
merge = diff3 -m CURRENT1 OLD CURRENT2 > NEW
will tell Unison to use the external diff3 program for
merging.
A large number of external merging programs are
available. For example, emacs users may find the
following convenient:
merge2 = emacs -q --eval '(ediff-merge-files "CURRENT1" "CURRENT2"
nil "NEW")'
merge = emacs -q --eval '(ediff-merge-files-with-ancestor
"CURRENT1" "CURRENT2" "OLD" nil "NEW")'
(These commands are displayed here on two lines to avoid
running off the edge of the page. In your preference
file, each should be written on a single line.)
o If the external program exits without leaving any file
at the path NEW, Unison considers the merge to have
failed. If the merge program writes a file called NEW
but exits with a non-zero status code, then Unison
considers the merge to have succeeded but to have
generated conflicts. In this case, it attempts to invoke
an external editor so that the user can resolve the
conflicts. The value of the editor preference controls
what editor is invoked by Unison. The default is emacs.
o Please send us suggestions for other useful values of
the merge2 and merge preferences -- we'd like to give
several examples in the manual.
* Smaller changes:
+ When one preference file includes another, unison no longer
adds the suffix '.prf' to the included file by default. If a
file with precisely the given name exists in the .unison
directory, it will be used; otherwise Unison will add .prf,
as it did before. (This change means that included preference
files can be named blah.include instead of blah.prf, so that
unison will not offer them in its 'choose a preference file'
dialog.)
+ For Linux systems, we now offer both a statically linked and
a dynamically linked executable. The static one is larger,
but will probably run on more systems, since it doesn't
depend on the same versions of dynamically linked library
modules being available.
+ Fixed the force and prefer preferences, which were getting
the propagation direction exactly backwards.
+ Fixed a bug in the startup code that would cause unison to
crash when the default profile (~/.unison/default.prf) does
not exist.
+ Fixed a bug where, on the run when a profile is first
created, Unison would confusingly display the roots in
reverse order in the user interface.
* For developers:
+ We've added a module dependency diagram to the source
distribution, in src/DEPENDENCIES.ps, to help new prospective
developers with navigating the code.
Changes since 2.6.11:
* INCOMPATIBLE CHANGE: Archive format has changed.
* INCOMPATIBLE CHANGE: The startup sequence has been completely
rewritten and greatly simplified. The main user-visible change is
that the defaultpath preference has been removed. Its effect can
be approximated by using multiple profiles, with include
directives to incorporate common settings. All uses of defaultpath
in existing profiles should be changed to path.
Another change in startup behavior that will affect some users is
that it is no longer possible to specify roots both in the profile
and on the command line.
You can achieve a similar effect, though, by breaking your profile
into two:
default.prf =
root = blah
root = foo
include common
common.prf =
<everything else>
Now do
unison common root1 root2
when you want to specify roots explicitly.
* The -prefer and -force options have been extended to allow users
to specify that files with more recent modtimes should be
propagated, writing either -prefer newer or -force newer. (For
symmetry, Unison will also accept -prefer older or -force older.)
The -force older/newer options can only be used when -times is
also set.
The graphical user interface provides access to these facilities
on a one-off basis via the Actions menu.
* Names of roots can now be ``aliased'' to allow replicas to be
relocated without changing the name of the archive file where
Unison stores information between runs. (This feature is for
experts only. See the ``Archive Files'' section of the manual for
more information.)
* Graphical user-interface:
+ A new command is provided in the Synchronization menu for
switching to a new profile without restarting Unison from
scratch.
+ The GUI also supports one-key shortcuts for commonly used
profiles. If a profile contains a preference of the form 'key
= n', where n is a single digit, then pressing this key will
cause Unison to immediately switch to this profile and begin
synchronization again from scratch. (Any actions that may
have been selected for a set of changes currently being
displayed will be discarded.)
+ Each profile may include a preference 'label = <string>'
giving a descriptive string that described the options
selected in this profile. The string is listed along with the
profile name in the profile selection dialog, and displayed
in the top-right corner of the main Unison window.
* Minor:
+ Fixed a bug that would sometimes cause the 'diff' display to
order the files backwards relative to the main user
interface. (Thanks to Pascal Brisset for this fix.)
+ On Unix systems, the graphical version of Unison will check
the DISPLAY variable and, if it is not set, automatically
fall back to the textual user interface.
+ Synchronization paths (path preferences) are now matched
against the ignore preferences. So if a path is both
specified in a path preference and ignored, it will be
skipped.
+ Numerous other bugfixes and small improvements.
Changes since 2.6.1:
* The synchronization of modification times has been disabled for
directories.
* Preference files may now include lines of the form include <name>,
which will cause name.prf to be read at that point.
* The synchronization of permission between Windows and Unix now
works properly.
* A binding CYGWIN=binmode in now added to the environment so that
the Cygwin port of OpenSSH works properly in a non-Cygwin context.
* The servercmd and addversionno preferences can now be used
together: -addversionno appends an appropriate -NNN to the server
command, which is found by using the value of the -servercmd
preference if there is one, or else just unison.
* Both '-pref=val' and '-pref val' are now allowed for boolean
values. (The former can be used to set a preference to false.)
* Lot of small bugs fixed.
Changes since 2.5.31:
* The log preference is now set to true by default, since the log
file seems useful for most users.
* Several miscellaneous bugfixes (most involving symlinks).
Changes since 2.5.25:
* INCOMPATIBLE CHANGE: Archive format has changed (again).
* Several significant bugs introduced in 2.5.25 have been fixed.
Changes since 2.5.1:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* New functionality:
+ Unison now synchronizes file modtimes, user-ids, and
group-ids.
These new features are controlled by a set of new
preferences, all of which are currently false by default.
o When the times preference is set to true, file
modification times are propaged. (Because the
representations of time may not have the same
granularity on both replicas, Unison may not always be
able to make the modtimes precisely equal, but it will
get them as close as the operating systems involved
allow.)
o When the owner preference is set to true, file ownership
information is synchronized.
o When the group preference is set to true, group
information is synchronized.
o When the numericIds preference is set to true, owner and
group information is synchronized numerically. By
default, owner and group numbers are converted to names
on each replica and these names are synchronized. (The
special user id 0 and the special group 0 are never
mapped via user/group names even if this preference is
not set.)
+ Added an integer-valued preference perms that can be used to
control the propagation of permission bits. The value of this
preference is a mask indicating which permission bits should
be synchronized. It is set by default to 0o1777: all bits but
the set-uid and set-gid bits are synchronised (synchronizing
theses latter bits can be a security hazard). If you want to
synchronize all bits, you can set the value of this
preference to -1.
+ Added a log preference (default false), which makes Unison
keep a complete record of the changes it makes to the
replicas. By default, this record is written to a file called
unison.log in the user's home directory (the value of the
HOME environment variable). If you want it someplace else,
set the logfile preference to the full pathname you want
Unison to use.
+ Added an ignorenot preference that maintains a set of
patterns for paths that should definitely not be ignored,
whether or not they match an ignore pattern. (That is, a path
will now be ignored iff it matches an ignore pattern and does
not match any ignorenot patterns.)
* User-interface improvements:
+ Roots are now displayed in the user interface in the same
order as they were given on the command line or in the
preferences file.
+ When the batch preference is set, the graphical user
interface no longer waits for user confirmation when it
displays a warning message: it simply pops up an advisory
window with a Dismiss button at the bottom and keeps on
going.
+ Added a new preference for controlling how many status
messages are printed during update detection: statusdepth
controls the maximum depth for paths on the local machine
(longer paths are not displayed, nor are non-directory
paths). The value should be an integer; default is 1.
+ Removed the trace and silent preferences. They did not seem
very useful, and there were too many preferences for
controlling output in various ways.
+ The text UI now displays just the default command (the one
that will be used if the user just types <return>) instead of
all available commands. Typing ? will print the full list of
possibilities.
+ The function that finds the canonical hostname of the local
host (which is used, for example, in calculating the name of
the archive file used to remember which files have been
synchronized) normally uses the gethostname operating system
call. However, if the environment variable
UNISONLOCALHOSTNAME is set, its value will now be used
instead. This makes it easier to use Unison in situations
where a machine's name changes frequently (e.g., because it
is a laptop and gets moved around a lot).
+ File owner and group are now displayed in the ``detail
window'' at the bottom of the screen, when unison is
configured to synchronize them.
* For hackers:
+ Updated to Jacques Garrigue's new version of lablgtk, which
means we can throw away our local patched version.
If you're compiling the GTK version of unison from sources,
you'll need to update your copy of lablgtk to the developers
release, available from
http://wwwfun.kurims.kyoto-u.ac.jp/soft/olabl/lablgtk.html
(Warning: installing lablgtk under Windows is currently a bit
challenging.)
+ The TODO.txt file (in the source distribution) has been
cleaned up and reorganized. The list of pending tasks should
be much easier to make sense of, for people that may want to
contribute their programming energies. There is also a
separate file BUGS.txt for open bugs.
+ The Tk user interface has been removed (it was not being
maintained and no longer compiles).
+ The debug preference now prints quite a bit of additional
information that should be useful for identifying sources of
problems.
+ The version number of the remote server is now checked right
away during the connection setup handshake, rather than
later. (Somebody sent a bug report of a server crash that
turned out to come from using inconsistent versions: better
to check this earlier and in a way that can't crash either
client or server.)
+ Unison now runs correctly on 64-bit architectures (e.g. Alpha
linux). We will not be distributing binaries for these
architectures ourselves (at least for a while) but if someone
would like to make them available, we'll be glad to provide a
link to them.
* Bug fixes:
+ Pattern matching (e.g. for ignore) is now case-insensitive
when Unison is in case-insensitive mode (i.e., when one of
the replicas is on a windows machine).
+ Some people had trouble with mysterious failures during
propagation of updates, where files would be falsely reported
as having changed during synchronization. This should be
fixed.
+ Numerous smaller fixes.
Changes since 2.4.1:
* Added a number of 'sorting modes' for the user interface. By
default, conflicting changes are displayed at the top, and the
rest of the entries are sorted in alphabetical order. This
behavior can be changed in the following ways:
+ Setting the sortnewfirst preference to true causes newly
created files to be displayed before changed files.
+ Setting sortbysize causes files to be displayed in increasing
order of size.
+ Giving the preference sortfirst=<pattern> (where <pattern> is
a path descriptor in the same format as 'ignore' and 'follow'
patterns, causes paths matching this pattern to be displayed
first.
+ Similarly, giving the preference sortlast=<pattern> causes
paths matching this pattern to be displayed last.
The sorting preferences are described in more detail in the user
manual. The sortnewfirst and sortbysize flags can also be accessed
from the 'Sort' menu in the grpahical user interface.
* Added two new preferences that can be used to change unison's
fundamental behavior to make it more like a mirroring tool instead
of a synchronizer.
+ Giving the preference prefer with argument <root> (by adding
-prefer <root> to the command line or prefer=<root>) to your
profile) means that, if there is a conflict, the contents of
<root> should be propagated to the other replica (with no
questions asked). Non-conflicting changes are treated as
usual.
+ Giving the preference force with argument <root> will make
unison resolve all differences in favor of the given root,
even if it was the other replica that was changed.
These options should be used with care! (More information is
available in the manual.)
* Small changes:
+ Changed default answer to 'Yes' in all two-button dialogs in
the graphical interface (this seems more intuitive).
+ The rsync preference has been removed (it was used to
activate rsync compression for file transfers, but rsync
compression is now enabled by default).
+ In the text user interface, the arrows indicating which
direction changes are being propagated are printed
differently when the user has overridded Unison's default
recommendation (====> instead of ---->). This matches the
behavior of the graphical interface, which displays such
arrows in a different color.
+ Carriage returns (Control-M's) are ignored at the ends of
lines in profiles, for Windows compatibility.
+ All preferences are now fully documented in the user manual.
Changes since 2.3.12:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* New/improved functionality:
+ A new preference -sortbysize controls the order in which
changes are displayed to the user: when it is set to true,
the smallest changed files are displayed first. (The default
setting is false.)
+ A new preference -sortnewfirst causes newly created files to
be listed before other updates in the user interface.
+ We now allow the ssh protocol to specify a port.
+ Incompatible change: The unison: protocol is deprecated, and
we added file: and socket:. You may have to modify your
profiles in the .unison directory. If a replica is specified
without an explicit protocol, we now assume it refers to a
file. (Previously "//saul/foo" meant to use SSH to connect to
saul, then access the foo directory. Now it means to access
saul via a remote file mechanism such as samba; the old
effect is now achieved by writing ssh://saul/foo.)
+ Changed the startup sequence for the case where roots are
given but no profile is given on the command line. The new
behavior is to use the default profile (creating it if it
does not exist), and temporarily override its roots. The
manual claimed that this case would work by reading no
profile at all, but AFAIK this was never true.
+ In all user interfaces, files with conflicts are always
listed first
+ A new preference 'sshversion' can be used to control which
version of ssh should be used to connect to the server. Legal
values are 1 and 2. (Default is empty, which will make unison
use whatever version of ssh is installed as the default 'ssh'
command.)
+ The situation when the permissions of a file was updated the
same on both side is now handled correctly (we used to report
a spurious conflict)
* Improvements for the Windows version:
+ The fact that filenames are treated case-insensitively under
Windows should now be handled correctly. The exact behavior
is described in the cross-platform section of the manual.
+ It should be possible to synchronize with Windows shares,
e.g., //host/drive/path.
+ Workarounds to the bug in syncing root directories in
Windows. The most difficult thing to fix is an ocaml bug:
Unix.opendir fails on c: in some versions of Windows.
* Improvements to the GTK user interface (the Tk interface is no
longer being maintained):
+ The UI now displays actions differently (in blue) when they
have been explicitly changed by the user from Unison's
default recommendation.
+ More colorful appearance.
+ The initial profile selection window works better.
+ If any transfers failed, a message to this effect is
displayed along with 'Synchronization complete' at the end of
the transfer phase (in case they may have scrolled off the
top).
+ Added a global progress meter, displaying the percentage of
total bytes that have been transferred so far.
* Improvements to the text user interface:
+ The file details will be displayed automatically when a
conflict is been detected.
+ when a warning is generated (e.g. for a temporary file left
over from a previous run of unison) Unison will no longer
wait for a response if it is running in -batch mode.
+ The UI now displays a short list of possible inputs each time
it waits for user interaction.
+ The UI now quits immediately (rather than looping back and
starting the interaction again) if the user presses 'q' when
asked whether to propagate changes.
+ Pressing 'g' in the text user interface will proceed
immediately with propagating updates, without asking any more
questions.
* Documentation and installation changes:
+ The manual now includes a FAQ, plus sections on common
problems and on tricks contributed by users.
+ Both the download page and the download directory explicitly
say what are the current stable and beta-test version
numbers.
+ The OCaml sources for the up-to-the-minute developers'
version (not guaranteed to be stable, or even to compile, at
any given time!) are now available from the download page.
+ Added a subsection to the manual describing cross-platform
issues (case conflicts, illegal filenames)
* Many small bug fixes and random improvements.
Changes since 2.3.1:
* Several bug fixes. The most important is a bug in the rsync module
that would occasionally cause change propagation to fail with a
'rename' error.
Changes since 2.2:
* The multi-threaded transport system is now disabled by default.
(It is not stable enough yet.)
* Various bug fixes.
* A new experimental feature:
The final component of a -path argument may now be the wildcard
specifier *. When Unison sees such a path, it expands this path on
the client into into the corresponding list of paths by listing
the contents of that directory.
Note that if you use wildcard paths from the command line, you
will probably need to use quotes or a backslash to prevent the *
from being interpreted by your shell.
If both roots are local, the contents of the first one will be
used for expanding wildcard paths. (Nb: this is the first one
after the canonization step -- i.e., the one that is listed first
in the user interface -- not the one listed first on the command
line or in the preferences file.)
Changes since 2.1:
* The transport subsystem now includes an implementation by Sylvain
Gommier and Norman Ramsey of Tridgell and Mackerras's rsync
protocol. This protocol achieves much faster transfers when only a
small part of a large file has been changed by sending just diffs.
This feature is mainly helpful for transfers over slow links---on
fast local area networks it can actually degrade performance---so
we have left it off by default. Start unison with the -rsync
option (or put rsync=true in your preferences file) to turn it on.
* ``Progress bars'' are now diplayed during remote file transfers,
showing what percentage of each file has been transferred so far.
* The version numbering scheme has changed. New releases will now be
have numbers like 2.2.30, where the second component is
incremented on every significant public release and the third
component is the ``patch level.''
* Miscellaneous improvements to the GTK-based user interface.
* The manual is now available in PDF format.
* We are experimenting with using a multi-threaded transport
subsystem to transfer several files at the same time, making much
more effective use of available network bandwidth. This feature is
not completely stable yet, so by default it is disabled in the
release version of Unison.
If you want to play with the multi-threaded version, you'll need
to recompile Unison from sources (as described in the
documentation), setting the THREADS flag in Makefile.OCaml to
true. Make sure that your OCaml compiler has been installed with
the -with-pthreads configuration option. (You can verify this by
checking whether the file threads/threads.cma in the OCaml
standard library directory contains the string -lpthread near the
end.)
Changes since 1.292:
* Reduced memory footprint (this is especially important during the
first run of unison, where it has to gather information about all
the files in both repositories).
* Fixed a bug that would cause the socket server under NT to fail
after the client exits.
* Added a SHIFT modifier to the Ignore menu shortcut keys in GTK
interface (to avoid hitting them accidentally).
Changes since 1.231:
* Tunneling over ssh is now supported in the Windows version. See
the installation section of the manual for detailed instructions.
* The transport subsystem now includes an implementation of the
rsync protocol, built by Sylvain Gommier and Norman Ramsey. This
protocol achieves much faster transfers when only a small part of
a large file has been changed by sending just diffs. The rsync
feature is off by default in the current version. Use the -rsync
switch to turn it on. (Nb. We still have a lot of tuning to do:
you may not notice much speedup yet.)
* We're experimenting with a multi-threaded transport subsystem,
written by Jerome Vouillon. The downloadable binaries are still
single-threaded: if you want to try the multi-threaded version,
you'll need to recompile from sources. (Say make THREADS=true.)
Native thread support from the compiler is required. Use the
option -threads N to select the maximal number of concurrent
threads (default is 5). Multi-threaded and single-threaded
clients/servers can interoperate.
* A new GTK-based user interface is now available, thanks to Jacques
Garrigue. The Tk user interface still works, but we'll be shifting
development effort to the GTK interface from now on.
* OCaml 3.00 is now required for compiling Unison from sources. The
modules uitk and myfileselect have been changed to use labltk
instead of camltk. To compile the Tk interface in Windows, you
must have ocaml-3.00 and tk8.3. When installing tk8.3, put it in
c:\Tcl rather than the suggested c:\Program Files\Tcl, and be sure
to install the headers and libraries (which are not installed by
default).
* Added a new -addversionno switch, which causes unison to use
unison-<currentversionnumber> instead of just unison as the remote
server command. This allows multiple versions of unison to coexist
conveniently on the same server: whichever version is run on the
client, the same version will be selected on the server.
Changes since 1.219:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* This version fixes several annoying bugs, including:
+ Some cases where propagation of file permissions was not
working.
+ umask is now ignored when creating directories
+ directories are create writable, so that a read-only
directory and its contents can be propagated.
+ Handling of warnings generated by the server.
+ Synchronizing a path whose parent is not a directory on both
sides is now flagged as erroneous.
+ Fixed some bugs related to symnbolic links and nonexistant
roots.
o When a change (deletion or new contents) is propagated
onto a 'follow'ed symlink, the file pointed to by the
link is now changed. (We used to change the link itself,
which doesn't fit our assertion that 'follow' means the
link is completely invisible)
o When one root did not exist, propagating the other root
on top of it used to fail, becuase unison could not
calculate the working directory into which to write
changes. This should be fixed.
* A human-readable timestamp has been added to Unison's archive
files.
* The semantics of Path and Name regular expressions now correspond
better.
* Some minor improvements to the text UI (e.g. a command for going
back to previous items)
* The organization of the export directory has changed --- should be
easier to find / download things now.
Changes since 1.200:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* This version has not been tested extensively on Windows.
* Major internal changes designed to make unison safer to run at the
same time as the replicas are being changed by the user.
* Internal performance improvements.
Changes since 1.190:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* A number of internal functions have been changed to reduce the
amount of memory allocation, especially during the first
synchronization. This should help power users with very big
replicas.
* Reimplementation of low-level remote procedure call stuff, in
preparation for adding rsync-like smart file transfer in a later
release.
* Miscellaneous bug fixes.
Changes since 1.180:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* Fixed some small bugs in the interpretation of ignore patterns.
* Fixed some problems that were preventing the Windows version from
working correctly when click-started.
* Fixes to treatment of file permissions under Windows, which were
causing spurious reports of different permissions when
synchronizing between windows and unix systems.
* Fixed one more non-tail-recursive list processing function, which
was causing stack overflows when synchronizing very large
replicas.
Changes since 1.169:
* The text user interface now provides commands for ignoring files.
* We found and fixed some more non-tail-recursive list processing
functions. Some power users have reported success with very large
replicas.
* INCOMPATIBLE CHANGE: Files ending in .tmp are no longer ignored
automatically. If you want to ignore such files, put an
appropriate ignore pattern in your profile.
* INCOMPATIBLE CHANGE: The syntax of ignore and follow patterns has
changed. Instead of putting a line of the form
ignore = <regexp>
in your profile (.unison/default.prf), you should put:
ignore = Regexp <regexp>
Moreover, two other styles of pattern are also recognized:
ignore = Name <name>
matches any path in which one component matches <name>, while
ignore = Path <path>
matches exactly the path <path>.
Standard ``globbing'' conventions can be used in <name> and
<path>:
+ a ? matches any single character except /
+ a * matches any sequence of characters not including /
+ [xyz] matches any character from the set {x, y, z }
+ {a,bb,ccc} matches any one of a, bb, or ccc.
See the user manual for some examples.
Changes since 1.146:
* Some users were reporting stack overflows when synchronizing huge
directories. We found and fixed some non-tail-recursive list
processing functions, which we hope will solve the problem. Please
give it a try and let us know.
* Major additions to the documentation.
Changes since 1.142:
* Major internal tidying and many small bugfixes.
* Major additions to the user manual.
* Unison can now be started with no arguments -- it will prompt
automatically for the name of a profile file containing the roots
to be synchronized. This makes it possible to start the graphical
UI from a desktop icon.
* Fixed a small bug where the text UI on NT was raising a 'no such
signal' exception.
Changes since 1.139:
* The precompiled windows binary in the last release was compiled
with an old OCaml compiler, causing propagation of permissions not
to work (and perhaps leading to some other strange behaviors we've
heard reports about). This has been corrected. If you're using
precompiled binaries on Windows, please upgrade.
* Added a -debug command line flag, which controls debugging of
various modules. Say -debug XXX to enable debug tracing for module
XXX, or -debug all to turn on absolutely everything.
* Fixed a small bug where the text UI on NT was raising a 'no such
signal' exception.
Changes since 1.111:
* INCOMPATIBLE CHANGE: The names and formats of the preference files
in the .unison directory have changed. In particular:
+ the file ``prefs'' should be renamed to default.prf
+ the contents of the file ``ignore'' should be merged into
default.prf. Each line of the form REGEXP in ignore should
become a line of the form ignore = REGEXP in default.prf.
* Unison now handles permission bits and symbolic links. See the
manual for details.
* You can now have different preference files in your .unison
directory. If you start unison like this
unison profilename
(i.e. with just one ``anonymous'' command-line argument), then the
file ~/.unison/profilename.prf will be loaded instead of
default.prf.
* Some improvements to terminal handling in the text user interface
* Added a switch -killServer that terminates the remote server
process when the unison client is shutting down, even when using
sockets for communication. (By default, a remote server created
using ssh/rsh is terminated automatically, while a socket server
is left running.)
* When started in 'socket server' mode, unison prints 'server
started' on stderr when it is ready to accept connections. (This
may be useful for scripts that want to tell when a socket-mode
server has finished initalization.)
* We now make a nightly mirror of our current internal development
tree, in case anyone wants an up-to-the-minute version to hack
around with.
* Added a file CONTRIB with some suggestions for how to help us make
Unison better.
Changes in Version 2.9.20
Changes since 2.9.1:
* Added a preference maxthreads that can be used to limit the number
of simultaneous file transfers.
* Added a backupdir preference, which controls where backup files
are stored.
* Basic support added for OSX. In particular, Unison now recognizes
when one of the hosts being synchronized is running OSX and
switches to a case-insensitive treatment of filenames (i.e., 'foo'
and 'FOO' are considered to be the same file). (OSX is not yet
fully working, however: in particular, files with resource forks
will not be synchronized correctly.)
* The same hash used to form the archive name is now also added to
the names of the temp files created during file transfer. The
reason for this is that, during update detection, we are going to
silently delete any old temp files that we find along the way, and
we want to prevent ourselves from deleting temp files belonging to
other instances of Unison that may be running in parallel, e.g.
synchronizing with a different host. Thanks to Ruslan Ermilov for
this suggestion.
* Several small user interface improvements
* Documentation
+ FAQ and bug reporting instructions have been split out as
separate HTML pages, accessible directly from the unison web
page.
+ Additions to FAQ, in particular suggestions about performance
tuning.
* Makefile
+ Makefile.OCaml now sets UISTYLE=text or UISTYLE=gtk
automatically, depending on whether it finds lablgtk
installed
+ Unison should now compile ``out of the box'' under OSX
Changes since 2.8.1:
* Changing profile works again under Windows
* File movement optimization: Unison now tries to use local copy
instead of transfer for moved or copied files. It is controled by
a boolean option ``xferbycopying''.
* Network statistics window (transfer rate, amount of data
transferred). [NB: not available in Windows-Cygwin version.]
* symlinks work under the cygwin version (which is dynamically
linked).
* Fixed potential deadlock when synchronizing between Windows and
Unix
* Small improvements:
+ If neither the
tt USERPROFILE nor the
tt HOME environment variables are set, then Unison will put
its temporary commit log (called
tt DANGER.README) into the directory named by the
tt UNISON environment variable, if any; otherwise it will use
tt C:.
+ alternative set of values for fastcheck: yes = true; no =
false; default = auto.
+ -silent implies -contactquietly
* Source code:
+ Code reorganization and tidying. (Started breaking up some of
the basic utility modules so that the non-unison-specific
stuff can be made available for other projects.)
+ several Makefile and docs changes (for release);
+ further comments in ``update.ml'';
+ connection information is not stored in global variables
anymore.
Changes since 2.7.78:
* Small bugfix to textual user interface under Unix (to avoid
leaving the terminal in a bad state where it would not echo inputs
after Unison exited).
Changes since 2.7.39:
* Improvements to the main web page (stable and beta version docs
are now both accessible).
* User manual revised.
* Added some new preferences:
+ ``sshcmd'' and ``rshcmd'' for specifying paths to ssh and rsh
programs.
+ ``contactquietly'' for suppressing the ``contacting server''
message during Unison startup (under the graphical UI).
* Bug fixes:
+ Fixed small bug in UI that neglected to change the displayed
column headers if loading a new profile caused the roots to
change.
+ Fixed a bug that would put the text UI into an infinite loop
if it encountered a conflict when run in batch mode.
+ Added some code to try to fix the display of non-Ascii
characters in filenames on Windows systems in the GTK UI.
(This code is currently untested---if you're one of the
people that had reported problems with display of non-ascii
filenames, we'd appreciate knowing if this actually fixes
things.)
+ `-prefer/-force newer' works properly now. (The bug was
reported by Sebastian Urbaniak and Sean Fulton.)
* User interface and Unison behavior:
+ Renamed `Proceed' to `Go' in the graphical UI.
+ Added exit status for the textual user interface.
+ Paths that are not synchronized because of conflicts or
errors during update detection are now noted in the log file.
+ [END] messages in log now use a briefer format
+ Changed the text UI startup sequence so that
tt ./unison -ui text will use the default profile instead of
failing.
+ Made some improvements to the error messages.
+ Added some debugging messages to remote.ml.
Changes since 2.7.7:
* Incorporated, once again, a multi-threaded transport sub-system.
It transfers several files at the same time, thereby making much
more effective use of available network bandwidth. Unlike the
earlier attempt, this time we do not rely on the native thread
library of OCaml. Instead, we implement a light-weight,
non-preemptive multi-thread library in OCaml directly. This
version appears stable.
Some adjustments to unison are made to accommodate the
multi-threaded version. These include, in particular, changes to
the user interface and logging, for example:
+ Two log entries for each transferring task, one for the
beginning, one for the end.
+ Suppressed warning messages against removing temp files left
by a previous unison run, because warning does not work
nicely under multi-threading. The temp file names are made
less likely to coincide with the name of a file created by
the user. They take the form
.#<filename>.<serial>.unison.tmp.
* Added a new command to the GTK user interface: pressing 'f' causes
Unison to start a new update detection phase, using as paths just
those paths that have been detected as changed and not yet marked
as successfully completed. Use this command to quickly restart
Unison on just the set of paths still needing attention after a
previous run.
* Made the ignorecase preference user-visible, and changed the
initialization code so that it can be manually set to true, even
if neither host is running Windows. (This may be useful, e.g.,
when using Unison running on a Unix system with a FAT volume
mounted.)
* Small improvements and bug fixes:
+ Errors in preference files now generate fatal errors rather
than warnings at startup time. (I.e., you can't go on from
them.) Also, we fixed a bug that was preventing these
warnings from appearing in the text UI, so some users who
have been running (unsuspectingly) with garbage in their
prefs files may now get error reports.
+ Error reporting for preference files now provides file name
and line number.
+ More intelligible message in the case of identical change to
the same files: ``Nothing to do: replicas have been changed
only in identical ways since last sync.''
+ Files with prefix '.#' excluded when scanning for preference
files.
+ Rsync instructions are send directly instead of first
marshaled.
+ Won't try forever to get the fingerprint of a continuously
changing file: unison will give up after certain number of
retries.
+ Other bug fixes, including the one reported by Peter Selinger
(force=older preference not working).
* Compilation:
+ Upgraded to the new OCaml 3.04 compiler, with the LablGtk
1.2.3 library (patched version used for compiling under
Windows).
+ Added the option to compile unison on the Windows platform
with Cygwin GNU C compiler. This option only supports
building dynamically linked unison executables.
Changes since 2.7.4:
* Fixed a silly (but debilitating) bug in the client startup
sequence.
Changes since 2.7.1:
* Added addprefsto preference, which (when set) controls which
preference file new preferences (e.g. new ignore patterns) are
added to.
* Bug fix: read the initial connection header one byte at a time, so
that we don't block if the header is shorter than expected. (This
bug did not affect normal operation --- it just made it hard to
tell when you were trying to use Unison incorrectly with an old
version of the server, since it would hang instead of giving an
error message.)
Changes since 2.6.59:
* Changed fastcheck from a boolean to a string preference. Its legal
values are yes (for a fast check), no (for a safe check), or
default (for a fast check---which also happens to be safe---when
running on Unix and a safe check when on Windows). The default is
default.
* Several preferences have been renamed for consistency. All
preference names are now spelled out in lowercase. For backward
compatibility, the old names still work, but they are not
mentioned in the manual any more.
* The temp files created by the 'diff' and 'merge' commands are now
named by prepending a new prefix to the file name, rather than
appending a suffix. This should avoid confusing diff/merge
programs that depend on the suffix to guess the type of the file
contents.
* We now set the keepalive option on the server socket, to make sure
that the server times out if the communication link is
unexpectedly broken.
* Bug fixes:
+ When updating small files, Unison now closes the destination
file.
+ File permissions are properly updated when the file is behind
a followed link.
+ Several other small fixes.
Changes since 2.6.38:
* Major Windows performance improvement!
We've added a preference fastcheck that makes Unison look only at
a file's creation time and last-modified time to check whether it
has changed. This should result in a huge speedup when checking
for updates in large replicas.
When this switch is set, Unison will use file creation times as
'pseudo inode numbers' when scanning Windows replicas for updates,
instead of reading the full contents of every file. This may cause
Unison to miss propagating an update if the create time,
modification time, and length of the file are all unchanged by the
update (this is not easy to achieve, but it can be done). However,
Unison will never overwrite such an update with a change from the
other replica, since it always does a safe check for updates just
before propagating a change. Thus, it is reasonable to use this
switch most of the time and occasionally run Unison once with
fastcheck set to false, if you are worried that Unison may have
overlooked an update.
Warning: This change is has not yet been thoroughly field-tested.
If you set the fastcheck preference, pay careful attention to what
Unison is doing.
* New functionality: centralized backups and merging
+ This version incorporates two pieces of major new
functionality, implemented by Sylvain Roy during a summer
internship at Penn: a centralized backup facility that keeps
a full backup of (selected files in) each replica, and a
merging feature that allows Unison to invoke an external
file-merging tool to resolve conflicting changes to
individual files.
+ Centralized backups:
o Unison now maintains full backups of the
last-synchronized versions of (some of) the files in
each replica; these function both as backups in the
usual sense and as the ``common version'' when invoking
external merge programs.
o The backed up files are stored in a directory
/.unison/backup on each host. (The name of this
directory can be changed by setting the environment
variable UNISONBACKUPDIR.)
o The predicate backup controls which files are actually
backed up: giving the preference 'backup = Path *'
causes backing up of all files.
o Files are added to the backup directory whenever unison
updates its archive. This means that
# When unison reconstructs its archive from scratch
(e.g., because of an upgrade, or because the
archive files have been manually deleted), all
files will be backed up.
# Otherwise, each file will be backed up the first
time unison propagates an update for it.
o The preference backupversions controls how many previous
versions of each file are kept. The default is 2 (i.e.,
the last synchronized version plus one backup).
o For backward compatibility, the backups preference is
also still supported, but backup is now preferred.
o It is OK to manually delete files from the backup
directory (or to throw away the directory itself).
Before unison uses any of these files for anything
important, it checks that its fingerprint matches the
one that it expects.
+ Merging:
o Both user interfaces offer a new 'merge' command,
invoked by pressing 'm' (with a changed file selected).
o The actual merging is performed by an external program.
The preferences merge and merge2 control how this
program is invoked. If a backup exists for this file
(see the backup preference), then the merge preference
is used for this purpose; otherwise merge2 is used. In
both cases, the value of the preference should be a
string representing the command that should be passed to
a shell to invoke the merge program. Within this string,
the special substrings CURRENT1, CURRENT2, NEW, and OLD
may appear at any point. Unison will substitute these as
follows before invoking the command:
# CURRENT1 is replaced by the name of the local copy
of the file;
# CURRENT2 is replaced by the name of a temporary
file, into which the contents of the remote copy of
the file have been transferred by Unison prior to
performing the merge;
# NEW is replaced by the name of a temporary file
that Unison expects to be written by the merge
program when it finishes, giving the desired new
contents of the file; and
# OLD is replaced by the name of the backed up copy
of the original version of the file (i.e., its
state at the end of the last successful run of
Unison), if one exists (applies only to merge, not
merge2).
For example, on Unix systems setting the merge
preference to
merge = diff3 -m CURRENT1 OLD CURRENT2 > NEW
will tell Unison to use the external diff3 program for
merging.
A large number of external merging programs are
available. For example, emacs users may find the
following convenient:
merge2 = emacs -q --eval '(ediff-merge-files "CURRENT1" "CURRENT2"
nil "NEW")'
merge = emacs -q --eval '(ediff-merge-files-with-ancestor
"CURRENT1" "CURRENT2" "OLD" nil "NEW")'
(These commands are displayed here on two lines to avoid
running off the edge of the page. In your preference
file, each should be written on a single line.)
o If the external program exits without leaving any file
at the path NEW, Unison considers the merge to have
failed. If the merge program writes a file called NEW
but exits with a non-zero status code, then Unison
considers the merge to have succeeded but to have
generated conflicts. In this case, it attempts to invoke
an external editor so that the user can resolve the
conflicts. The value of the editor preference controls
what editor is invoked by Unison. The default is emacs.
o Please send us suggestions for other useful values of
the merge2 and merge preferences -- we'd like to give
several examples in the manual.
* Smaller changes:
+ When one preference file includes another, unison no longer
adds the suffix '.prf' to the included file by default. If a
file with precisely the given name exists in the .unison
directory, it will be used; otherwise Unison will add .prf,
as it did before. (This change means that included preference
files can be named blah.include instead of blah.prf, so that
unison will not offer them in its 'choose a preference file'
dialog.)
+ For Linux systems, we now offer both a statically linked and
a dynamically linked executable. The static one is larger,
but will probably run on more systems, since it doesn't
depend on the same versions of dynamically linked library
modules being available.
+ Fixed the force and prefer preferences, which were getting
the propagation direction exactly backwards.
+ Fixed a bug in the startup code that would cause unison to
crash when the default profile (~/.unison/default.prf) does
not exist.
+ Fixed a bug where, on the run when a profile is first
created, Unison would confusingly display the roots in
reverse order in the user interface.
* For developers:
+ We've added a module dependency diagram to the source
distribution, in src/DEPENDENCIES.ps, to help new prospective
developers with navigating the code.
Changes since 2.6.11:
* INCOMPATIBLE CHANGE: Archive format has changed.
* INCOMPATIBLE CHANGE: The startup sequence has been completely
rewritten and greatly simplified. The main user-visible change is
that the defaultpath preference has been removed. Its effect can
be approximated by using multiple profiles, with include
directives to incorporate common settings. All uses of defaultpath
in existing profiles should be changed to path.
Another change in startup behavior that will affect some users is
that it is no longer possible to specify roots both in the profile
and on the command line.
You can achieve a similar effect, though, by breaking your profile
into two:
default.prf =
root = blah
root = foo
include common
common.prf =
<everything else>
Now do
unison common root1 root2
when you want to specify roots explicitly.
* The -prefer and -force options have been extended to allow users
to specify that files with more recent modtimes should be
propagated, writing either -prefer newer or -force newer. (For
symmetry, Unison will also accept -prefer older or -force older.)
The -force older/newer options can only be used when -times is
also set.
The graphical user interface provides access to these facilities
on a one-off basis via the Actions menu.
* Names of roots can now be ``aliased'' to allow replicas to be
relocated without changing the name of the archive file where
Unison stores information between runs. (This feature is for
experts only. See the ``Archive Files'' section of the manual for
more information.)
* Graphical user-interface:
+ A new command is provided in the Synchronization menu for
switching to a new profile without restarting Unison from
scratch.
+ The GUI also supports one-key shortcuts for commonly used
profiles. If a profile contains a preference of the form 'key
= n', where n is a single digit, then pressing this key will
cause Unison to immediately switch to this profile and begin
synchronization again from scratch. (Any actions that may
have been selected for a set of changes currently being
displayed will be discarded.)
+ Each profile may include a preference 'label = <string>'
giving a descriptive string that described the options
selected in this profile. The string is listed along with the
profile name in the profile selection dialog, and displayed
in the top-right corner of the main Unison window.
* Minor:
+ Fixed a bug that would sometimes cause the 'diff' display to
order the files backwards relative to the main user
interface. (Thanks to Pascal Brisset for this fix.)
+ On Unix systems, the graphical version of Unison will check
the DISPLAY variable and, if it is not set, automatically
fall back to the textual user interface.
+ Synchronization paths (path preferences) are now matched
against the ignore preferences. So if a path is both
specified in a path preference and ignored, it will be
skipped.
+ Numerous other bugfixes and small improvements.
Changes since 2.6.1:
* The synchronization of modification times has been disabled for
directories.
* Preference files may now include lines of the form include <name>,
which will cause name.prf to be read at that point.
* The synchronization of permission between Windows and Unix now
works properly.
* A binding CYGWIN=binmode in now added to the environment so that
the Cygwin port of OpenSSH works properly in a non-Cygwin context.
* The servercmd and addversionno preferences can now be used
together: -addversionno appends an appropriate -NNN to the server
command, which is found by using the value of the -servercmd
preference if there is one, or else just unison.
* Both '-pref=val' and '-pref val' are now allowed for boolean
values. (The former can be used to set a preference to false.)
* Lot of small bugs fixed.
Changes since 2.5.31:
* The log preference is now set to true by default, since the log
file seems useful for most users.
* Several miscellaneous bugfixes (most involving symlinks).
Changes since 2.5.25:
* INCOMPATIBLE CHANGE: Archive format has changed (again).
* Several significant bugs introduced in 2.5.25 have been fixed.
Changes since 2.5.1:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* New functionality:
+ Unison now synchronizes file modtimes, user-ids, and
group-ids.
These new features are controlled by a set of new
preferences, all of which are currently false by default.
o When the times preference is set to true, file
modification times are propaged. (Because the
representations of time may not have the same
granularity on both replicas, Unison may not always be
able to make the modtimes precisely equal, but it will
get them as close as the operating systems involved
allow.)
o When the owner preference is set to true, file ownership
information is synchronized.
o When the group preference is set to true, group
information is synchronized.
o When the numericIds preference is set to true, owner and
group information is synchronized numerically. By
default, owner and group numbers are converted to names
on each replica and these names are synchronized. (The
special user id 0 and the special group 0 are never
mapped via user/group names even if this preference is
not set.)
+ Added an integer-valued preference perms that can be used to
control the propagation of permission bits. The value of this
preference is a mask indicating which permission bits should
be synchronized. It is set by default to 0o1777: all bits but
the set-uid and set-gid bits are synchronised (synchronizing
theses latter bits can be a security hazard). If you want to
synchronize all bits, you can set the value of this
preference to -1.
+ Added a log preference (default false), which makes Unison
keep a complete record of the changes it makes to the
replicas. By default, this record is written to a file called
unison.log in the user's home directory (the value of the
HOME environment variable). If you want it someplace else,
set the logfile preference to the full pathname you want
Unison to use.
+ Added an ignorenot preference that maintains a set of
patterns for paths that should definitely not be ignored,
whether or not they match an ignore pattern. (That is, a path
will now be ignored iff it matches an ignore pattern and does
not match any ignorenot patterns.)
* User-interface improvements:
+ Roots are now displayed in the user interface in the same
order as they were given on the command line or in the
preferences file.
+ When the batch preference is set, the graphical user
interface no longer waits for user confirmation when it
displays a warning message: it simply pops up an advisory
window with a Dismiss button at the bottom and keeps on
going.
+ Added a new preference for controlling how many status
messages are printed during update detection: statusdepth
controls the maximum depth for paths on the local machine
(longer paths are not displayed, nor are non-directory
paths). The value should be an integer; default is 1.
+ Removed the trace and silent preferences. They did not seem
very useful, and there were too many preferences for
controlling output in various ways.
+ The text UI now displays just the default command (the one
that will be used if the user just types <return>) instead of
all available commands. Typing ? will print the full list of
possibilities.
+ The function that finds the canonical hostname of the local
host (which is used, for example, in calculating the name of
the archive file used to remember which files have been
synchronized) normally uses the gethostname operating system
call. However, if the environment variable
UNISONLOCALHOSTNAME is set, its value will now be used
instead. This makes it easier to use Unison in situations
where a machine's name changes frequently (e.g., because it
is a laptop and gets moved around a lot).
+ File owner and group are now displayed in the ``detail
window'' at the bottom of the screen, when unison is
configured to synchronize them.
* For hackers:
+ Updated to Jacques Garrigue's new version of lablgtk, which
means we can throw away our local patched version.
If you're compiling the GTK version of unison from sources,
you'll need to update your copy of lablgtk to the developers
release, available from
http://wwwfun.kurims.kyoto-u.ac.jp/soft/olabl/lablgtk.html
(Warning: installing lablgtk under Windows is currently a bit
challenging.)
+ The TODO.txt file (in the source distribution) has been
cleaned up and reorganized. The list of pending tasks should
be much easier to make sense of, for people that may want to
contribute their programming energies. There is also a
separate file BUGS.txt for open bugs.
+ The Tk user interface has been removed (it was not being
maintained and no longer compiles).
+ The debug preference now prints quite a bit of additional
information that should be useful for identifying sources of
problems.
+ The version number of the remote server is now checked right
away during the connection setup handshake, rather than
later. (Somebody sent a bug report of a server crash that
turned out to come from using inconsistent versions: better
to check this earlier and in a way that can't crash either
client or server.)
+ Unison now runs correctly on 64-bit architectures (e.g. Alpha
linux). We will not be distributing binaries for these
architectures ourselves (at least for a while) but if someone
would like to make them available, we'll be glad to provide a
link to them.
* Bug fixes:
+ Pattern matching (e.g. for ignore) is now case-insensitive
when Unison is in case-insensitive mode (i.e., when one of
the replicas is on a windows machine).
+ Some people had trouble with mysterious failures during
propagation of updates, where files would be falsely reported
as having changed during synchronization. This should be
fixed.
+ Numerous smaller fixes.
Changes since 2.4.1:
* Added a number of 'sorting modes' for the user interface. By
default, conflicting changes are displayed at the top, and the
rest of the entries are sorted in alphabetical order. This
behavior can be changed in the following ways:
+ Setting the sortnewfirst preference to true causes newly
created files to be displayed before changed files.
+ Setting sortbysize causes files to be displayed in increasing
order of size.
+ Giving the preference sortfirst=<pattern> (where <pattern> is
a path descriptor in the same format as 'ignore' and 'follow'
patterns, causes paths matching this pattern to be displayed
first.
+ Similarly, giving the preference sortlast=<pattern> causes
paths matching this pattern to be displayed last.
The sorting preferences are described in more detail in the user
manual. The sortnewfirst and sortbysize flags can also be accessed
from the 'Sort' menu in the grpahical user interface.
* Added two new preferences that can be used to change unison's
fundamental behavior to make it more like a mirroring tool instead
of a synchronizer.
+ Giving the preference prefer with argument <root> (by adding
-prefer <root> to the command line or prefer=<root>) to your
profile) means that, if there is a conflict, the contents of
<root> should be propagated to the other replica (with no
questions asked). Non-conflicting changes are treated as
usual.
+ Giving the preference force with argument <root> will make
unison resolve all differences in favor of the given root,
even if it was the other replica that was changed.
These options should be used with care! (More information is
available in the manual.)
* Small changes:
+ Changed default answer to 'Yes' in all two-button dialogs in
the graphical interface (this seems more intuitive).
+ The rsync preference has been removed (it was used to
activate rsync compression for file transfers, but rsync
compression is now enabled by default).
+ In the text user interface, the arrows indicating which
direction changes are being propagated are printed
differently when the user has overridded Unison's default
recommendation (====> instead of ---->). This matches the
behavior of the graphical interface, which displays such
arrows in a different color.
+ Carriage returns (Control-M's) are ignored at the ends of
lines in profiles, for Windows compatibility.
+ All preferences are now fully documented in the user manual.
Changes since 2.3.12:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* New/improved functionality:
+ A new preference -sortbysize controls the order in which
changes are displayed to the user: when it is set to true,
the smallest changed files are displayed first. (The default
setting is false.)
+ A new preference -sortnewfirst causes newly created files to
be listed before other updates in the user interface.
+ We now allow the ssh protocol to specify a port.
+ Incompatible change: The unison: protocol is deprecated, and
we added file: and socket:. You may have to modify your
profiles in the .unison directory. If a replica is specified
without an explicit protocol, we now assume it refers to a
file. (Previously "//saul/foo" meant to use SSH to connect to
saul, then access the foo directory. Now it means to access
saul via a remote file mechanism such as samba; the old
effect is now achieved by writing ssh://saul/foo.)
+ Changed the startup sequence for the case where roots are
given but no profile is given on the command line. The new
behavior is to use the default profile (creating it if it
does not exist), and temporarily override its roots. The
manual claimed that this case would work by reading no
profile at all, but AFAIK this was never true.
+ In all user interfaces, files with conflicts are always
listed first
+ A new preference 'sshversion' can be used to control which
version of ssh should be used to connect to the server. Legal
values are 1 and 2. (Default is empty, which will make unison
use whatever version of ssh is installed as the default 'ssh'
command.)
+ The situation when the permissions of a file was updated the
same on both side is now handled correctly (we used to report
a spurious conflict)
* Improvements for the Windows version:
+ The fact that filenames are treated case-insensitively under
Windows should now be handled correctly. The exact behavior
is described in the cross-platform section of the manual.
+ It should be possible to synchronize with Windows shares,
e.g., //host/drive/path.
+ Workarounds to the bug in syncing root directories in
Windows. The most difficult thing to fix is an ocaml bug:
Unix.opendir fails on c: in some versions of Windows.
* Improvements to the GTK user interface (the Tk interface is no
longer being maintained):
+ The UI now displays actions differently (in blue) when they
have been explicitly changed by the user from Unison's
default recommendation.
+ More colorful appearance.
+ The initial profile selection window works better.
+ If any transfers failed, a message to this effect is
displayed along with 'Synchronization complete' at the end of
the transfer phase (in case they may have scrolled off the
top).
+ Added a global progress meter, displaying the percentage of
total bytes that have been transferred so far.
* Improvements to the text user interface:
+ The file details will be displayed automatically when a
conflict is been detected.
+ when a warning is generated (e.g. for a temporary file left
over from a previous run of unison) Unison will no longer
wait for a response if it is running in -batch mode.
+ The UI now displays a short list of possible inputs each time
it waits for user interaction.
+ The UI now quits immediately (rather than looping back and
starting the interaction again) if the user presses 'q' when
asked whether to propagate changes.
+ Pressing 'g' in the text user interface will proceed
immediately with propagating updates, without asking any more
questions.
* Documentation and installation changes:
+ The manual now includes a FAQ, plus sections on common
problems and on tricks contributed by users.
+ Both the download page and the download directory explicitly
say what are the current stable and beta-test version
numbers.
+ The OCaml sources for the up-to-the-minute developers'
version (not guaranteed to be stable, or even to compile, at
any given time!) are now available from the download page.
+ Added a subsection to the manual describing cross-platform
issues (case conflicts, illegal filenames)
* Many small bug fixes and random improvements.
Changes since 2.3.1:
* Several bug fixes. The most important is a bug in the rsync module
that would occasionally cause change propagation to fail with a
'rename' error.
Changes since 2.2:
* The multi-threaded transport system is now disabled by default.
(It is not stable enough yet.)
* Various bug fixes.
* A new experimental feature:
The final component of a -path argument may now be the wildcard
specifier *. When Unison sees such a path, it expands this path on
the client into into the corresponding list of paths by listing
the contents of that directory.
Note that if you use wildcard paths from the command line, you
will probably need to use quotes or a backslash to prevent the *
from being interpreted by your shell.
If both roots are local, the contents of the first one will be
used for expanding wildcard paths. (Nb: this is the first one
after the canonization step -- i.e., the one that is listed first
in the user interface -- not the one listed first on the command
line or in the preferences file.)
Changes since 2.1:
* The transport subsystem now includes an implementation by Sylvain
Gommier and Norman Ramsey of Tridgell and Mackerras's rsync
protocol. This protocol achieves much faster transfers when only a
small part of a large file has been changed by sending just diffs.
This feature is mainly helpful for transfers over slow links---on
fast local area networks it can actually degrade performance---so
we have left it off by default. Start unison with the -rsync
option (or put rsync=true in your preferences file) to turn it on.
* ``Progress bars'' are now diplayed during remote file transfers,
showing what percentage of each file has been transferred so far.
* The version numbering scheme has changed. New releases will now be
have numbers like 2.2.30, where the second component is
incremented on every significant public release and the third
component is the ``patch level.''
* Miscellaneous improvements to the GTK-based user interface.
* The manual is now available in PDF format.
* We are experimenting with using a multi-threaded transport
subsystem to transfer several files at the same time, making much
more effective use of available network bandwidth. This feature is
not completely stable yet, so by default it is disabled in the
release version of Unison.
If you want to play with the multi-threaded version, you'll need
to recompile Unison from sources (as described in the
documentation), setting the THREADS flag in Makefile.OCaml to
true. Make sure that your OCaml compiler has been installed with
the -with-pthreads configuration option. (You can verify this by
checking whether the file threads/threads.cma in the OCaml
standard library directory contains the string -lpthread near the
end.)
Changes since 1.292:
* Reduced memory footprint (this is especially important during the
first run of unison, where it has to gather information about all
the files in both repositories).
* Fixed a bug that would cause the socket server under NT to fail
after the client exits.
* Added a SHIFT modifier to the Ignore menu shortcut keys in GTK
interface (to avoid hitting them accidentally).
Changes since 1.231:
* Tunneling over ssh is now supported in the Windows version. See
the installation section of the manual for detailed instructions.
* The transport subsystem now includes an implementation of the
rsync protocol, built by Sylvain Gommier and Norman Ramsey. This
protocol achieves much faster transfers when only a small part of
a large file has been changed by sending just diffs. The rsync
feature is off by default in the current version. Use the -rsync
switch to turn it on. (Nb. We still have a lot of tuning to do:
you may not notice much speedup yet.)
* We're experimenting with a multi-threaded transport subsystem,
written by Jerome Vouillon. The downloadable binaries are still
single-threaded: if you want to try the multi-threaded version,
you'll need to recompile from sources. (Say make THREADS=true.)
Native thread support from the compiler is required. Use the
option -threads N to select the maximal number of concurrent
threads (default is 5). Multi-threaded and single-threaded
clients/servers can interoperate.
* A new GTK-based user interface is now available, thanks to Jacques
Garrigue. The Tk user interface still works, but we'll be shifting
development effort to the GTK interface from now on.
* OCaml 3.00 is now required for compiling Unison from sources. The
modules uitk and myfileselect have been changed to use labltk
instead of camltk. To compile the Tk interface in Windows, you
must have ocaml-3.00 and tk8.3. When installing tk8.3, put it in
c:\Tcl rather than the suggested c:\Program Files\Tcl, and be sure
to install the headers and libraries (which are not installed by
default).
* Added a new -addversionno switch, which causes unison to use
unison-<currentversionnumber> instead of just unison as the remote
server command. This allows multiple versions of unison to coexist
conveniently on the same server: whichever version is run on the
client, the same version will be selected on the server.
Changes since 1.219:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* This version fixes several annoying bugs, including:
+ Some cases where propagation of file permissions was not
working.
+ umask is now ignored when creating directories
+ directories are create writable, so that a read-only
directory and its contents can be propagated.
+ Handling of warnings generated by the server.
+ Synchronizing a path whose parent is not a directory on both
sides is now flagged as erroneous.
+ Fixed some bugs related to symnbolic links and nonexistant
roots.
o When a change (deletion or new contents) is propagated
onto a 'follow'ed symlink, the file pointed to by the
link is now changed. (We used to change the link itself,
which doesn't fit our assertion that 'follow' means the
link is completely invisible)
o When one root did not exist, propagating the other root
on top of it used to fail, becuase unison could not
calculate the working directory into which to write
changes. This should be fixed.
* A human-readable timestamp has been added to Unison's archive
files.
* The semantics of Path and Name regular expressions now correspond
better.
* Some minor improvements to the text UI (e.g. a command for going
back to previous items)
* The organization of the export directory has changed --- should be
easier to find / download things now.
Changes since 1.200:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* This version has not been tested extensively on Windows.
* Major internal changes designed to make unison safer to run at the
same time as the replicas are being changed by the user.
* Internal performance improvements.
Changes since 1.190:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* A number of internal functions have been changed to reduce the
amount of memory allocation, especially during the first
synchronization. This should help power users with very big
replicas.
* Reimplementation of low-level remote procedure call stuff, in
preparation for adding rsync-like smart file transfer in a later
release.
* Miscellaneous bug fixes.
Changes since 1.180:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* Fixed some small bugs in the interpretation of ignore patterns.
* Fixed some problems that were preventing the Windows version from
working correctly when click-started.
* Fixes to treatment of file permissions under Windows, which were
causing spurious reports of different permissions when
synchronizing between windows and unix systems.
* Fixed one more non-tail-recursive list processing function, which
was causing stack overflows when synchronizing very large
replicas.
Changes since 1.169:
* The text user interface now provides commands for ignoring files.
* We found and fixed some more non-tail-recursive list processing
functions. Some power users have reported success with very large
replicas.
* INCOMPATIBLE CHANGE: Files ending in .tmp are no longer ignored
automatically. If you want to ignore such files, put an
appropriate ignore pattern in your profile.
* INCOMPATIBLE CHANGE: The syntax of ignore and follow patterns has
changed. Instead of putting a line of the form
ignore = <regexp>
in your profile (.unison/default.prf), you should put:
ignore = Regexp <regexp>
Moreover, two other styles of pattern are also recognized:
ignore = Name <name>
matches any path in which one component matches <name>, while
ignore = Path <path>
matches exactly the path <path>.
Standard ``globbing'' conventions can be used in <name> and
<path>:
+ a ? matches any single character except /
+ a * matches any sequence of characters not including /
+ [xyz] matches any character from the set {x, y, z }
+ {a,bb,ccc} matches any one of a, bb, or ccc.
See the user manual for some examples.
Changes since 1.146:
* Some users were reporting stack overflows when synchronizing huge
directories. We found and fixed some non-tail-recursive list
processing functions, which we hope will solve the problem. Please
give it a try and let us know.
* Major additions to the documentation.
Changes since 1.142:
* Major internal tidying and many small bugfixes.
* Major additions to the user manual.
* Unison can now be started with no arguments -- it will prompt
automatically for the name of a profile file containing the roots
to be synchronized. This makes it possible to start the graphical
UI from a desktop icon.
* Fixed a small bug where the text UI on NT was raising a 'no such
signal' exception.
Changes since 1.139:
* The precompiled windows binary in the last release was compiled
with an old OCaml compiler, causing propagation of permissions not
to work (and perhaps leading to some other strange behaviors we've
heard reports about). This has been corrected. If you're using
precompiled binaries on Windows, please upgrade.
* Added a -debug command line flag, which controls debugging of
various modules. Say -debug XXX to enable debug tracing for module
XXX, or -debug all to turn on absolutely everything.
* Fixed a small bug where the text UI on NT was raising a 'no such
signal' exception.
Changes since 1.111:
* INCOMPATIBLE CHANGE: The names and formats of the preference files
in the .unison directory have changed. In particular:
+ the file ``prefs'' should be renamed to default.prf
+ the contents of the file ``ignore'' should be merged into
default.prf. Each line of the form REGEXP in ignore should
become a line of the form ignore = REGEXP in default.prf.
* Unison now handles permission bits and symbolic links. See the
manual for details.
* You can now have different preference files in your .unison
directory. If you start unison like this
unison profilename
(i.e. with just one ``anonymous'' command-line argument), then the
file ~/.unison/profilename.prf will be loaded instead of
default.prf.
* Some improvements to terminal handling in the text user interface
* Added a switch -killServer that terminates the remote server
process when the unison client is shutting down, even when using
sockets for communication. (By default, a remote server created
using ssh/rsh is terminated automatically, while a socket server
is left running.)
* When started in 'socket server' mode, unison prints 'server
started' on stderr when it is ready to accept connections. (This
may be useful for scripts that want to tell when a socket-mode
server has finished initalization.)
* We now make a nightly mirror of our current internal development
tree, in case anyone wants an up-to-the-minute version to hack
around with.
* Added a file CONTRIB with some suggestions for how to help us make
Unison better.
To unsubscribe from this group, send an email to:
unison-announce-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
| scam | en |
"
Wikilinking
Hi, and thanks for your work on the English Wikipedia.
I noticed an article you worked on. Just a short note to point out that we don’t normally link:
dates
years
commonly known geographical terms (including well-known country-names), and
common terms you’d look up in a dictionary (unless significantly technical).
This applies to infoboxes, too.
Thanks, and my best wishes.
(talk) " | toxic | en |
":Hi Summers95926. Please enter information about copyrights on the image page when you upload it. If it is fairuse, you can specify that there. If you have the authority to grant copyright permission to images then note than in the image upload page with something that can be verified. I am not an expert on the copyright issues within Wikipedia so you may want to ask a user more familiar with this for help. If you need further assistance, leave me a message and I will see what I can do. (talk)
" | toxic | en |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.