Re: [python-committers] [Infrastructure] [Pydotorg] XSS security issue

2013-07-16 Thread Ezio Melotti
Hi, On Mon, Jul 15, 2013 at 2:08 PM, R. David Murray wrote: > On Mon, 15 Jul 2013 11:09:08 +0300, Michael Foord > wrote: >> >> On 15 Jul 2013, at 11:05, "M.-A. Lemburg" wrote: >> >> > Who would be the one to contact for issues like these ? >> > >> > The case is rather urgent, since the XSS can

Re: [python-committers] IMPORTANT: Strip your repos if you pulled recently

2013-07-16 Thread Benjamin Peterson
You can just pull. 2013/7/16 Barry Warsaw : > On Jul 16, 2013, at 09:31 AM, Benjamin Peterson wrote: > >>Oops, the bad one is actually >> >>8889c9b5dd3a > > Uh, then how do we unstrip the other one? Or should we just re-clone and > ignore this ever happened? ;) > > -Barry > __

Re: [python-committers] IMPORTANT: Strip your repos if you pulled recently

2013-07-16 Thread Serhiy Storchaka
16.07.13 19:31, Benjamin Peterson написав(ла): Oops, the bad one is actually 8889c9b5dd3a Now I can pull! ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] IMPORTANT: Strip your repos if you pulled recently

2013-07-16 Thread Barry Warsaw
On Jul 16, 2013, at 09:31 AM, Benjamin Peterson wrote: >Oops, the bad one is actually > >8889c9b5dd3a Uh, then how do we unstrip the other one? Or should we just re-clone and ignore this ever happened? ;) -Barry ___ python-committers mailing list pyth

Re: [python-committers] IMPORTANT: Strip your repos if you pulled recently

2013-07-16 Thread Benjamin Peterson
Oops, the bad one is actually 8889c9b5dd3a 2013/7/16 Ronald Oussoren : > > On 16 Jul, 2013, at 18:03, Benjamin Peterson wrote: > >> It should be safe to continue pulling. Those revisions you see below >> are ones committed after I stripped the repo. > > Isn't the first one the stripped changeset

Re: [python-committers] IMPORTANT: Strip your repos if you pulled recently

2013-07-16 Thread Ronald Oussoren
On 16 Jul, 2013, at 18:03, Benjamin Peterson wrote: > It should be safe to continue pulling. Those revisions you see below > are ones committed after I stripped the repo. Isn't the first one the stripped changeset? Ronald > > 2013/7/16 Ronald Oussoren : >> >> On 16 Jul, 2013, at 5:46, Benj

Re: [python-committers] IMPORTANT: Strip your repos if you pulled recently

2013-07-16 Thread Benjamin Peterson
You should be completely safe if you didn't pull at all yesterday. 2013/7/16 Terry Reedy : > > > On 7/15/2013 11:46 PM, Benjamin Peterson wrote: >> >> If you have c3a510b22218 in your repo, you will need to strip it like this >> >> $ hg strip c3a510b22218 >> >> (make sure to have the mq extension

Re: [python-committers] IMPORTANT: Strip your repos if you pulled recently

2013-07-16 Thread Benjamin Peterson
It should be safe to continue pulling. Those revisions you see below are ones committed after I stripped the repo. 2013/7/16 Ronald Oussoren : > > On 16 Jul, 2013, at 5:46, Benjamin Peterson wrote: > >> If you have c3a510b22218 in your repo, you will need to strip it like this >> >> $ hg strip c3

Re: [python-committers] IMPORTANT: Strip your repos if you pulled recently

2013-07-16 Thread Ronald Oussoren
On 16 Jul, 2013, at 5:46, Benjamin Peterson wrote: > If you have c3a510b22218 in your repo, you will need to strip it like this > > $ hg strip c3a510b22218 > > (make sure to have the mq extension enabled) > > Sorry for the trouble. If I do that and run "hg incoming" I get a number of incomin

Re: [python-committers] IMPORTANT: Strip your repos if you pulled recently

2013-07-16 Thread Terry Reedy
On 7/15/2013 11:46 PM, Benjamin Peterson wrote: If you have c3a510b22218 in your repo, you will need to strip it like this $ hg strip c3a510b22218 (make sure to have the mq extension enabled) Does the subject mean that if I have not pulled recently (a day, at least), it will not get pulled