On Mon, 07 Feb 2011 20:38:28 -0200, Wesley Mesquita
wrote:
> [198/349] test_ossaudiodev
> test_ossaudiodev skipped -- [Errno 2] No such file or directory: '/dev/dsp'
This is normal since you don't have a /dev/dsp. That's what the
skip message means.
> [200/349] test_parser
> Expecting 's_push:
Hi all,
I starting to explore python 3k core development environment. So, sorry in
advance for any mistakes, but I really don't know what is the best list to
post this, since it not a "use of python" issue, and probably is not a dev
issue, it is more like a "dev env" question.
I have ran the test
Chris Withers wrote:
On 06/02/2011 15:25, Brian Curtin wrote:
So put the new path before the old path, or replace it? The current
patch appends to the end.
I believe the last path wins in Windows land, so that would be fine.
Actually, first one wins, as Windows starts at the beginning and st
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 Mon, Feb 7, 2011 at 15:46, Antoine Pitrou wrote:
> I'm not advocating anything in particular really. I think creating a
> named branch "foo" (or a bookmark? I've never used them but it sounds
> like they might do the trick) and then using "hg di -r py3k" to get the
> diff against upstream is ve
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
> > locally you really want to use something like named branches or mq to
>
On 07/02/2011 14:28, Antoine Pitrou wrote:
On Mon, 07 Feb 2011 13:27:31 +
Michael Foord wrote:
On 07/02/2011 12:25, Georg Brandl wrote:
Am 07.02.2011 00:21, schrieb Nick Coghlan:
On Mon, Feb 7, 2011 at 6:53 AM, Brett Cannon wrote:
I would rather not have new hg users have to install an
On Mon, 07 Feb 2011 13:27:31 +
Michael Foord wrote:
> On 07/02/2011 12:25, Georg Brandl wrote:
> > Am 07.02.2011 00:21, schrieb Nick Coghlan:
> >> On Mon, Feb 7, 2011 at 6:53 AM, Brett Cannon wrote:
> >>> I would rather not have new hg users have to install an extension just
> >>> to get a si
On Mon, 07 Feb 2011 13:26:28 +0100
Georg Brandl wrote:
> Am 06.02.2011 21:13, schrieb Brett Cannon:
>
> >>> To undo a patch, you can revert **all** changes made in your checkout::
> >>>
> >>> -svn revert -R .
> >>> +hg revert --all
> >>> +
> >>
> >> Or "hg revert -a", which is nicer to t
On 07/02/2011 12:25, Georg Brandl wrote:
Am 07.02.2011 00:21, schrieb Nick Coghlan:
On Mon, Feb 7, 2011 at 6:53 AM, Brett Cannon wrote:
I would rather not have new hg users have to install an extension just
to get a simple workflow going.
I may still keep my Rdiff-based FAQ entry around as an
Am 06.02.2011 21:13, schrieb Brett Cannon:
>>> To undo a patch, you can revert **all** changes made in your checkout::
>>>
>>> -svn revert -R .
>>> +hg revert --all
>>> +
>>
>> Or "hg revert -a", which is nicer to type.
>
> I prefer being explicit over implicit in the tutorial.
BTW, the
Am 07.02.2011 00:21, schrieb Nick Coghlan:
> On Mon, Feb 7, 2011 at 6:53 AM, Brett Cannon wrote:
>> I would rather not have new hg users have to install an extension just
>> to get a simple workflow going.
>
> I may still keep my Rdiff-based FAQ entry around as an example of how
> to get a collap
12 matches
Mail list logo
