On 2011-03-31, at 8:44 PM, Antoine Pitrou wrote:
> On Thu, 31 Mar 2011 18:20:53 -0700
> Raymond Hettinger wrote:
>>
>> Surely, we at least have control over our own CSS.
>> At http://hg.python.org/cpython/static/style-paper.css
>> there are two lines that control the alternating bars:
>>
>> .
On 2011-03-08, at 1:03 AM, Martin v. Löwis wrote:
>> Sorry, I didn't think that through. Revsets still have the power though:
>>
>> hg -R tmp.bundle diff -r'ancestor(.,default)' -r default
>>
>> (assuming your local repo is at the tip of default)
>
> I can't make this work. I'm using hg 1.6.4,
On 2011-03-07, at 2:30 PM, Brendan Cully wrote:
> On 2011-03-07, at 2:18 PM, Martin v. Löwis wrote:
>
>> Am 07.03.2011 23:09, schrieb Brendan Cully:
>>> On 2011-03-07, at 1:03 PM, Martin v. Löwis wrote:
>>>
>>>> I'd like to experiment with ad
On 2011-03-07, at 2:18 PM, Martin v. Löwis wrote:
> Am 07.03.2011 23:09, schrieb Brendan Cully:
>> On 2011-03-07, at 1:03 PM, Martin v. Löwis wrote:
>>
>>> I'd like to experiment with adding Rietveld support for reviewing
>>> remote repositories. For t
On 2011-03-07, at 1:03 PM, Martin v. Löwis wrote:
> I'd like to experiment with adding Rietveld support for reviewing
> remote repositories. For that, I'd need to create a single patch
> (programmatically) that covers all incoming changes. 'hg incoming -p'
> mostly works, but it may provide multip
On Monday, 07 February 2011 at 15:46, Antoine Pitrou wrote:
> On Mon, 07 Feb 2011 14:34:35 +
> Michael Foord wrote:
> > >>>
> > >> And from the description it sounds like rdiff will be very useful for
> > >> our usecase.
> > > I'm not sure it is really. When you commit multiple changesets
> >
On Sunday, 06 February 2011 at 12:13, Brett Cannon wrote:
> On Sun, Feb 6, 2011 at 08:15, Antoine Pitrou wrote:
> > On Sun, 06 Feb 2011 02:10:15 +0100
> > brett.cannon wrote:
> >>
> >> To create your patch, you should generate a unified diff from your
> >> checkout's
> >> top-level directory::
On Friday, 10 April 2009 at 15:05, P.J. Eby wrote:
> At 06:52 PM 4/10/2009 +1000, Nick Coghlan wrote:
>> This problem (slow application startup times due to too many imports at
>> startup, which can in turn can be due to top level imports for library
>> or framework functionality that a given appli
