Le lundi 15 juillet 2013 à 20:49 -0700, Benjamin Peterson a écrit :
> Okay, I fixed the repo. You may need to strip your repo per my last mail.
I'm a bit wary of what might happen on automated stuff (i.e. buildbots).
Regards
Antoine.
___
python-commi
Okay, I fixed the repo. You may need to strip your repo per my last mail.
2013/7/15 Benjamin Peterson :
> I accidently pushed a merge from 3.3 to default in the "3.3" branch. I
> think I'm going to have to strip it.
>
> --
> Regards,
> Benjamin
--
Regards,
Benjamin
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.
--
Regards,
Benjamin
___
python-committers mailing list
python-committers@python.o
There's no unwanted head to close. It's all on the 3.3 branch.
2013/7/15 Jason R. Coombs :
> The other option is you could 'close' the unwanted head and create a new
> head at the point before the unwanted merge.
>
>> -Original Message-
>> From: python-committers [mailto:python-committers-
The other option is you could 'close' the unwanted head and create a new
head at the point before the unwanted merge.
> -Original Message-
> From: python-committers [mailto:python-committers-
> bounces+jaraco=jaraco@python.org] On Behalf Of Benjamin Peterson
> Sent: Monday, 15 July, 20
I accidently pushed a merge from 3.3 to default in the "3.3" branch. I
think I'm going to have to strip it.
--
Regards,
Benjamin
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
On Mon, 15 Jul 2013 18:02:35 +0200, Antoine Pitrou wrote:
> On 2013-07-15 17:16, R. David Murray wrote:
> >
> >> I will make the password available to whoever is in charge, (Or they
> >> can just change the password themselves I don't care).
> >
> > I think the user should just be retired. My g
On 15 Jul, 2013, at 18:02, Antoine Pitrou wrote:
> On 2013-07-15 17:16, R. David Murray wrote:
>>> I will make the password available to whoever is in charge, (Or they
>>> can just change the password themselves I don't care).
>> I think the user should just be retired. My guess is that it date
On 2013-07-15 17:16, R. David Murray wrote:
I will make the password available to whoever is in charge, (Or they
can just change the password themselves I don't care).
I think the user should just be retired. My guess is that it dates
from
a time when we were less worried about bad actors c
On Mon, 15 Jul 2013 08:22:40 -0400, Donald Stufft wrote:
> So I was able to log in to the "nobody" account without a password
> (Why is this even possible?). It gave me powers to edit users and some
> other shit. I added a password to the nobody account since these lists
> are publicly available a
On Mon, Jul 15, 2013 at 9:33 AM, Brett Cannon wrote:
>
>
>
> On Mon, Jul 15, 2013 at 8:08 AM, R. David Murray wrote:
>
>> On Mon, 15 Jul 2013 11:09:08 +0300, Michael Foord <
>> mich...@voidspace.org.uk> wrote:
>> >
>> > On 15 Jul 2013, at 11:05, "M.-A. Lemburg" wrote:
>> >
>> > > Who would be th
On Mon, Jul 15, 2013 at 8:08 AM, R. David Murray wrote:
> On Mon, 15 Jul 2013 11:09:08 +0300, Michael Foord <
> mich...@voidspace.org.uk> 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 rathe
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 be used for stealing
> > session cookies on *.python.org.
> >
> > T
13 matches
Mail list logo
