Oh well done!! Both of those look very promising. Thanks very much!
Brian, do you want to give either or both of these a go and see
whether they behave on your system (when you are back at your Windows
machine of course).
Bill
On 13 April 2010 19:40, Nicholas Kinar wrote:
>
>> msysgit is comman
msysgit is command line is it not? We're really looking for a GUI solution.
As for bazaar, I'm really sold on git. It is technically extremely
proficient and seems to be extremely popular, so it is much easier to
please more people by using it.
Perhaps other GUIs for git on Windows wo
msysgit is command line is it not? We're really looking for a GUI solution.
As for bazaar, I'm really sold on git. It is technically extremely
proficient and seems to be extremely popular, so it is much easier to
please more people by using it.
Bill.
On 13 April 2010 19:30, Nicholas Kinar wrote
Yeah tortoise git seems to have problems though. It quite often
doesn't display the correct icons, so you have no idea which files
have local modifications.
Also when we tried using it before, the Windows line endings screw up
git. It believed that every line of the file had changed meaning
massiv
Next question is what to do about Windows. Brian Gladman will not be
using the command line and so we need to ensure that whatever we come
up with works smoothly for him. Relying on one of us to push changes
onto an svn repo somewhere and then to merge back when he makes
changes seems like too m
Yes that does work - it can be done on github. If you log in you can
even do it via the web interface with the fork button!! So everyone on
github can have their own repositories, like:
git://github.com/{username}/bsdnt.git
I'll probably keep mine on vennard.org.uk cause I've got that configured
Personally I like the idea of rabidly forking the "main" repository,
i.e. everyone maintain their own repo and let me know of patches and
I'll pull them onto the master repo. Everyone can track that and merge
patches into their own repos.
Does that work?
Next question is what to do about Windows.
Hi Bill,
Sorry for the delay.
Basically, we have two options:
* One, we all work off that repository and just push our work to our own
dedicated branches (git being distributed means we can do what we like
on our own local copies provided we push to the correct remote branch).
Someone will have
I've not used githib before. But there's now a git repo at:
g...@github.com:wbhart/bsdnt.git
So how do we make this work. Does everyone just push onto a branch there?
I can add your ssh public key if you provide it to me.
Bill.
On 12 April 2010 23:48, Bill Hart wrote:
> Yeah, I'll do a git re
Yeah, I'll do a git repo now, if I can remember how.
Note I haven't licensed my files BSD yet. I will if there is
sufficient interest to warrant it. So far there seems to be some
interest.
Bill.
On 12 April 2010 23:37, Antony Vennard wrote:
> I was just about to reply that OpenMP is supported i
I was just about to reply that OpenMP is supported in MSVC. I wouldn't
have suggested it for MPIR otherwise as it wouldn't build. icc is free
for non-commercial use on Linux, which this constitutes, and supports
OpenMP too. However, I think it does some funny business with binaries
i.e. optimising
Brian points out that MSVC has openMP support. As it is just pragmas
it'll be ignored by PCC (so long as we don't call OpenMP functions).
So yeah, why not. Let's fill the code with pragmas.
So we should target pcc, gcc, MSVC and possibly icc.
Six problems we have right off:
* no longlong.h (so f
On 12 April 2010 21:04, Antony Vennard wrote:
> Yes.
>
> Can we manage it with git? Is there a git repo already...?
There's no git repo yet. But yes, we have to manage it with git. svn
is too limiting.
But we'd need to give very careful thought to how we do Windows
support (git doesn't work very
Yes.
Can we manage it with git? Is there a git repo already...?
Can I write #pragma omp declarations all over it? I.e. can I start
parallelising things early on? I'll license all contributions on MPIR as
BSD which is easily compatible with LGPLv3 then I'm good, really,
providing I don't duplicate
Rather than talk about hypothetical code I wrote when I was thinking
of producing BSD licensed library, I may as well expose it:
http://sage.math.washington.edu/home/wbhart/mpir-bsd/
It has a magic makefile system such that if you drop files in, they
just build automatically.
Simply do make chec
15 matches
Mail list logo
