Here's the actual import with that filter:
[5] - https://github.com/slide/ipimport5/issues
On Tue, Mar 25, 2014 at 8:07 AM, Slide wrote:
> Ok, I didn't do the actual import, but there are 236 issues that would be
> migrated.
>
>
> On Tue, Mar 25, 2014 at 6:53 AM, Jeff Hardy wrote:
>
>> On Tue
Ok, I didn't do the actual import, but there are 236 issues that would be
migrated.
On Tue, Mar 25, 2014 at 6:53 AM, Jeff Hardy wrote:
> On Tue, Mar 25, 2014 at 1:28 PM, Slide wrote:
> > Here are four repos that show the different options
> >
> > [1] - Open issues from CodePlex only - 1007 iss
On Tue, Mar 25, 2014 at 1:50 PM, Jeff Hardy wrote:
> On Tue, Mar 25, 2014 at 10:23 AM, Pawel Jasinski
> wrote:
>> Here is my work in progress:
>> https://github.com/paweljasinski/ironpython3/compare/parser3
>> Comments are welcome.
>
> My initial thought is that it's way too big to be one commit.
On Tue, Mar 25, 2014 at 1:28 PM, Slide wrote:
> Here are four repos that show the different options
>
> [1] - Open issues from CodePlex only - 1007 issues migrated
> [2] - Open issues filtered by votes >= 1 - 763 issues migrated
> [3] - Open issues filtered by created/updated since 25/03/2013 - 11
hmmm, I didn't write my filtering that way, but I can probably add it...
On Tue, Mar 25, 2014 at 6:53 AM, Jeff Hardy wrote:
> On Tue, Mar 25, 2014 at 1:28 PM, Slide wrote:
> > Here are four repos that show the different options
> >
> > [1] - Open issues from CodePlex only - 1007 issues migrate
On Tue, Mar 25, 2014 at 1:25 PM, Pawel Jasinski
wrote:
> agree, it was a first point where ipy stopped complaining on startup :-)
> I am sure git offers a reasonable help, so I can split things into
> digestible (testable) pieces.
`git reset` will "undo" the commit back into the working tree, and
Here are four repos that show the different options
[1] - Open issues from CodePlex only - 1007 issues migrated
[2] - Open issues filtered by votes >= 1 - 763 issues migrated
[3] - Open issues filtered by created/updated since 25/03/2013 - 111 issues
migrated
[4] - Open issues filtered by votes >=
On Tue, Mar 25, 2014 at 10:23 AM, Pawel Jasinski
wrote:
> Here is my work in progress:
> https://github.com/paweljasinski/ironpython3/compare/parser3
> Comments are welcome.
My initial thought is that it's way too big to be one commit. :) it's
too much to digest or review all at once.
I also mad
Here is my work in progress:
https://github.com/paweljasinski/ironpython3/compare/parser3
Comments are welcome.
On Tue, Mar 25, 2014 at 10:56 AM, Jeff Hardy wrote:
> On Mon, Mar 24, 2014 at 3:47 PM, Pawel Jasinski
> wrote:
>> hi,
>>
>> I started to tinker with parser. Does anybody else work on p
On Mon, Mar 24, 2014 at 3:47 PM, Pawel Jasinski
wrote:
> hi,
>
> I started to tinker with parser. Does anybody else work on parser already?
One thing to watch for is that parts of the parser are auto-generated
by some Python scripts (there are comments in the files that say which
script was used)
Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New issue] add support for pymongo
--
ISSUES
1. [New issue] add support for pymongo
http://ironpython.codeplex.com/workitem/35075
User robde
11 matches
Mail list logo