[M3devel] Resend: Re: elego prjm build error

[Coleburn, Randy]

Rodney:

Thanks for this information.
I will have to find some time then to get smart on GIT.
Until then, I guess I'm out of luck getting updates and pushing commits.

Thanks,
Randy Coleburn

-----Original Message-----
From: Rodney M. Bates [mailto:rodney_bates at lcwb.coop] 
Sent: Friday, October 03, 2014 11:26 AM
To: Coleburn, Randy; m3devel
Subject: EXT:Re: [M3devel] Resend: Re: elego prjm build error

I am a still a very rank beginning git user, but a couple of comments.

I have the impression that the CVS repository is now read-only, which would mean not only that you can't update it, but that it is not tracking updates pushed to github.

Yes, you will need an entire separate subdirectory for your local git workspace.  Unlike CVS, it will contain a complete repository, including the entire history, locally.  "commit" will just commit to your local repository.  Although we are set up to treat the repo on the github site as the central one, as with CVS, git has no builtin concept of a central repository.  "push" and "pull" commands will sync between your local one and any arbitrary repo you specify.

On 10/02/2014 04:06 PM, Coleburn, Randy wrote:
> Rodney / Tony:
>
> Thanks.  I'll update via CVS and give it a try.
>
> BTW, I haven't yet moved over to GIT yet.
> Are both CVS and GIT being maintained?
> Are there instructions for moving to GIT?
> I will probably pursue using TortoiseGIT since I've used TortoiseCVS.
> Will I need a separate workspace for the GIT repo, or can it be done on top of my existing CVS repo?
>
> Thanks,
> Randy Coleburn
>
> -----Original Message-----
> From: Rodney M. Bates [mailto:rodney_bates at lcwb.coop]
> Sent: Thursday, October 02, 2014 4:03 PM
> To: Antony Hosking; m3devel
> Cc: m3devel; Coleburn, Randy
> Subject: EXT:Re: [M3devel] Resend: Re: elego prjm build error
>
> OK, there's the answer.  I changed 4 occurrences of "LongrealType" to "LongReal in elego/prjbase/src/m3makefile, and everything in elego compiled without a hitch.
>
> It will take me a bit to sort out pushing this to the github repo, as I think I have other things committed in my local repo that I may not be ready to push to github.
>
...

--
Rodney Bates
rodney.m.bates at acm.org