Benjamin Peterson writes:
> I will leave a few initial comments.
Thank you.
"Martin v. Löwis" writes:
> > In the case of http://bugs.python.org/issue1170> (“shlex have
> > problems with parsing unicode”), the problem is apparently addressed
> > by a patch, assigned to that issue since 2007-12
On 22/08/2009 7:09 PM, "Martin v. Löwis" wrote:
From my POV, this would be required in some form or another before such
a scheme could actually work. Without it we end up with an improved
win32text (good!)
I still think this would be actually bad.
Instead, a new extension should be written,
On 22/08/2009 6:52 PM, Stephen J. Turnbull wrote:
Mark Hammond writes:
> On 22/08/2009 2:46 PM, Stephen J. Turnbull wrote:
> Possibly - although I would expect the existing section names be reused
> when applied to a versioned file, I'd be more than happy for the hg guys
> to declare
On Fri, Aug 21, 2009 at 6:58 PM, Mark Hammond wrote:
> [encode]
> *.dsp=none:
> **=cleverencode:
>
> The end result should be that anything with 'none:' forms what you call an
> ignore list.
>
> Would that not meet your requirements?
It would, so I guess I'll hold off on digging into the hook cod
2009/8/22 Jeroen Ruigrok van der Werven :
> -On [20090822 21:30], Paul Moore (p.f.mo...@gmail.com) wrote:
>>I've just had a look on python.org, but couldn't immediately see a
>>pointer to instructions on what the process is to set up a buildbot.
>
> http://wiki.py
-On [20090822 21:30], Paul Moore (p.f.mo...@gmail.com) wrote:
>I've just had a look on python.org, but couldn't immediately see a
>pointer to instructions on what the process is to set up a buildbot.
http://wiki.python.org/moin/BuildBot comes to mind.
--
Jeroen Ruigrok van der W
I've just had a look on python.org, but couldn't immediately see a
pointer to instructions on what the process is to set up a buildbot.
There's a not on setting things up for pybots, but nothing on the core
buildbot setup.
The reason I'm asking is that I'm thinking of seeing if I could set up
a Wi
Stephen J. Turnbull wrote:
> Dirkjan Ochtman writes:
>
> > [Clients] cannot be trusted (e.g. I might put a win32text stub in
> > there somewhere that does nothing).
>
> Heck, just edit the .hgrules file, and do a Houdini on any and all
> handcuffs.
>
> Don't trust software, trust people -- but
Paul Moore writes:
> 2009/8/22 Martin Geisler :
>> Oh, we try to be very paranoid in Mercurial :-) That's why you don't
>> see any support for copying hgrc files when you clone and why hg wont
>> trust hgrc files not owned by you: it should be safe to do
>>
>> cd ~collegue/src/python
>> hg tip
2009/8/22 Martin Geisler :
> Oh, we try to be very paranoid in Mercurial :-) That's why you don't see
> any support for copying hgrc files when you clone and why hg wont trust
> hgrc files not owned by you: it should be safe to do
>
> cd ~collegue/src/python
> hg tip
So, is the implication there
"Stephen J. Turnbull" writes:
> Mark Hammond writes:
> > On 22/08/2009 2:46 PM, Stephen J. Turnbull wrote:
>
> > Possibly - although I would expect the existing section names be reused
> > when applied to a versioned file, I'd be more than happy for the hg guys
> > to declare new names are
"Stephen J. Turnbull" writes:
> Mark Hammond writes:
>
> [extensions]
> required_for_commit = win32text,some_other_ext
>
> That might require a change to hg's ini file semantics if currently it
> refuses to parse [extension] sections in versioned hgrcs.
It doesn' refuse anything like that. When
> What is the procedure for finding out why an issue hasn't progressed?
It's fairly simple: just read through the issue, and it should be
obvious. In the specific case, no committer has ever commented on
the issue, so chances are high that no committer has ever *seen*
the issue.
> I don't want to
> From my POV, this would be required in some form or another before such
> a scheme could actually work. Without it we end up with an improved
> win32text (good!)
I still think this would be actually bad.
Instead, a new extension should be written, with a name that does not
have "win32" as a su
Dirkjan Ochtman writes:
> [Clients] cannot be trusted (e.g. I might put a win32text stub in
> there somewhere that does nothing).
Heck, just edit the .hgrules file, and do a Houdini on any and all
handcuffs.
Don't trust software, trust people -- but help them avoid thoughtless
mistakes.
__
Mark Hammond writes:
> On 22/08/2009 2:46 PM, Stephen J. Turnbull wrote:
> Possibly - although I would expect the existing section names be reused
> when applied to a versioned file, I'd be more than happy for the hg guys
> to declare new names are appropriate for this.
If there's already a
On Sat, Aug 22, 2009 at 01:17, Martin Geisler wrote:
> In the general case, you can specify an extension to be enabled by
> filename:
>
> [extensions]
> foo = ~/src/foo
>
> So if I can enable an extension like that on your system, I might be
> evil and commit a bad extension *and* enable it at th
17 matches
Mail list logo
