[M3devel] github

[Dragiša Durić]

Problem really looks like that. It did not happen to me, but I was using strict workflow.

Git is like that - a sharp knife. But it gives a lot back, I believe we will all reap benefits from it RSN.

Good news 2 - build problems on AMD64_DARWIN I had just went away with few fixes - one I am sure of is one already commited. I am trying few other gcc variants now to see what OSX Mavericks gcc options are good for cm3 build.

One thing I know already - C backend has a problem, some ASSERT fails. As it is my first priority to have cm3 running I only changed backend mode from C to 3.

More coming.

On 27 Aug 2014, at 17:47, Darko Volaric <lists at darko.org> wrote:

> Apparently this is because of the name change of the repository, or its owner. You'll need to do a clone of the new repository before commits to avoid the problem.
> 
> Dragisha is fixing it up... 
> 
> 
> 
> 
> On Tue, Aug 26, 2014 at 2:12 PM, Tony Hosking <hosking at cs.purdue.edu> wrote:
> Something weird happened on my recent git commit.
> Why did I end up committing thousands of files?
> 
> Antony Hosking | Associate Professor | Computer Science | Purdue University
> 305 N. University Street | West Lafayette | IN 47907 | USA
> Mobile +1 765 427 5484
> 
> 
> 
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20140827/83be651d/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20140827/83be651d/attachment-0002.sig>