On Mon, Nov 10, 2008 at 7:39 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 10, 2008 at 2:12 AM, Brian Granger <[EMAIL PROTECTED]> wrote:
>>
Use
git://git.sympy.org/sympy
>>>
>>> Yes, that's our official repository, but Brian wanted to see my new
>>> patches, that are still w
On Mon, Nov 10, 2008 at 2:12 AM, Brian Granger <[EMAIL PROTECTED]> wrote:
>
>>> Use
>>> git://git.sympy.org/sympy
>>
>> Yes, that's our official repository, but Brian wanted to see my new
>> patches, that are still waiting for the review. See my previous email
>> how to get them.
>
> Actually, for
>> Use
>> git://git.sympy.org/sympy
>
> Yes, that's our official repository, but Brian wanted to see my new
> patches, that are still waiting for the review. See my previous email
> how to get them.
Actually, for now, I just wanted my master to track the mainline sympy
repo (which I guess is git:
On Mon, Nov 10, 2008 at 12:55 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 10, 2008 at 12:33 AM, Brian Granger <[EMAIL PROTECTED]> wrote:
>>
>> Ondrej,
>>
>> My git clone has as its origin this: git://github.com/certik/sympy
>>
>> But, when I do git pull on master, it doesn't pick up
On Mon, Nov 10, 2008 at 12:33 AM, Brian Granger <[EMAIL PROTECTED]> wrote:
>
> Ondrej,
>
> My git clone has as its origin this: git://github.com/certik/sympy
>
> But, when I do git pull on master, it doesn't pick up any of the
> recent changes to the main git repo. I wanted to get the recent
> pr
On Mon, Nov 10, 2008 at 9:51 AM, Sebastian <[EMAIL PROTECTED]> wrote:
>
>
>> My git clone has as its origin this: git://github.com/certik/sympy
>>
> Use
> git://git.sympy.org/sympy
Yes, that's our official repository, but Brian wanted to see my new
patches, that are still waiting for the review.
> My git clone has as its origin this: git://github.com/certik/sympy
>
Use
git://git.sympy.org/sympy
Sebastian
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"sympy" group.
To post to this group, send email to
