Re: [Plplot-devel] Best git version for Windows?

[Alan W. Irwin]

On 2017-03-10 11:02-0500 Jim Dishaw wrote:

>
>> On Feb 21, 2017, at 4:45 PM, Alan W. Irwin  wrote:
>>
>> @Jim, Phil, and Arjen:
>>
>> I used the git SF server just this morning with no issues.  Also, for
>> the reasons discussed in README.developers you should avoid all gui
>> versions or "enhanced" versions of git (i.e., try to stick as much as
>> possible to the real thing).  Bearing those constraints in mind, that
>> file recommends  for Windows
>> users, but I just discovered from looking at that site that it has
>> been obsoleted and msysgit developers now recommend using the "Git for
>> Windows"  version of git instead.
>> (I confirmed from that website it considers itself light-weight
>> [check!] and it does have a command-line version [check!]).  So please
>> give the command-line version of that project a try, and let us know
>> whether it works well for you (which would allow us to recommend that
>> Windows version of git in our README.developers file).
>>
>

> I just pushed my first patch set after recovering from my VM
failure.  I’m using the Git for Windows and everything appears to have
worked.

Hi Jim:

I am glad to hear you are up and running with "Git on Windows". I
confirm your push process worked.

Your good result motivated me to make additional changes (commit
658796c) to README.developers concerning git command-line availability
(including replacing the msysgit reference with the "Git for Windows"
reference).  As part of the research for that update, I consulted
, and it
turns out that book has also now been updated to replace its previous
reference to msysgit with "Git for Windows".  So that book's
recommendation and your own good experience leave me confident that we
are doing the right thing to recommend "Git for Windows" in addition
(now) to other Windows git command-line possibilities such as the git
packages from either Cygwin or MinGW-w64/MSYS2.

Alan
__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__

--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Re: [Plplot-devel] Best git version for Windows?

[Jim Dishaw]

> On Feb 21, 2017, at 4:45 PM, Alan W. Irwin  wrote:
> 
> @Jim, Phil, and Arjen:
> 
> I used the git SF server just this morning with no issues.  Also, for
> the reasons discussed in README.developers you should avoid all gui
> versions or "enhanced" versions of git (i.e., try to stick as much as
> possible to the real thing).  Bearing those constraints in mind, that
> file recommends  for Windows
> users, but I just discovered from looking at that site that it has
> been obsoleted and msysgit developers now recommend using the "Git for
> Windows"  version of git instead.
> (I confirmed from that website it considers itself light-weight
> [check!] and it does have a command-line version [check!]).  So please
> give the command-line version of that project a try, and let us know
> whether it works well for you (which would allow us to recommend that
> Windows version of git in our README.developers file).
> 

I just pushed my first patch set after recovering from my VM failure.  I’m 
using the Git for Windows and everything appears to have worked.  I would 
appreciate it if someone who uses windows can double-check that the wingdi 
driver works.  One can print directly from the wingdi window by right-clicking 
and selecting Print


--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Re: [Plplot-devel] Best git version for Windows?

[Phil Rosenberg]

Hi Jim
Good luck with the restoration. If this helps for the future then as a
windows user you can get 1 TB of OneDrive space as part of an Office
365 subscription. I basically symlinked my Documents folder into my
OneDrive folder so that everything I do gets continually synced with
the cloud.

Anyway, as far as git is concerned I use Git within Cygwin even for my
Windows development. I always feel the Linux environment that goes
along with this gives the best development environment. You could
probably get an identical setup by using the new Bash on Ubuntu on
Windows feature if you are using Windows 10. Windows now ships with
the ability to install a native but stripped down (command line only)
version of Ubuntu within Windows. This runs native Linux executables
and you have access to apt-get so it's pretty handy!

Phil

On 21 February 2017 at 21:45, Alan W. Irwin  wrote:
> To Jim, Phil, and Arjen:
>
> On 2017-02-20 00:38-0500 Jim Dishaw wrote:
>
>> I need your help to sort out git.  Long story short, I had a disk
>
> corruption on the VM that I was doing my development work and had to
> recover my work.  I manage to get my wingdi driver recovered from the
> smoking heap.
>
> @Jim:
>
> My sympathies concerning your hardware troubles.  I am especially
> sensitive to that issue because I just went through a hardware scare
> myself (spent a lot of yesterday running hardware tests when I ran
> into the *.pyc corruption issue).  But amazingly this 9-year-old
> hardware (with an ASUS motherboard which might be the reason for this
> longevity) still passes all hardware tests, and I have concluded (with
> a fair amount of confidence) that the *.pyc corruption issue must be
> due to some Python bug.  So I plan to keep using this hardware for
> a while longer.
>
>> Unfortunately, I appear to be having problems with the git
>
> repository on SourceForge and I am not sure of the cause—I cannot even
> clone from SourceForge.
>
> @Jim, Phil, and Arjen:
>
> I used the git SF server just this morning with no issues.  Also, for
> the reasons discussed in README.developers you should avoid all gui
> versions or "enhanced" versions of git (i.e., try to stick as much as
> possible to the real thing).  Bearing those constraints in mind, that
> file recommends  for Windows
> users, but I just discovered from looking at that site that it has
> been obsoleted and msysgit developers now recommend using the "Git for
> Windows"  version of git instead.
> (I confirmed from that website it considers itself light-weight
> [check!] and it does have a command-line version [check!]).  So please
> give the command-line version of that project a try, and let us know
> whether it works well for you (which would allow us to recommend that
> Windows version of git in our README.developers file).
>
> Alan
> __
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __
>
> Linux-powered Science
> __

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Re: [Plplot-devel] Best git version for Windows?

[Arjen Markus]

Hi Alan,

Never tried it before - I have sofar relied on Cygwin to do the job. I made a 
note to look into this after my holiday next week.

Regards,

Arjen

DISCLAIMER: This message is intended exclusively for the addressee(s) and may 
contain confidential and privileged information. If you are not the intended 
recipient please notify the sender immediately and destroy this message. 
Unauthorized use, disclosure or copying of this message is strictly prohibited. 
The foundation 'Stichting Deltares', which has its seat at Delft, The 
Netherlands, Commercial Registration Number 41146461, is not liable in any way 
whatsoever for consequences and/or damages resulting from the improper, 
incomplete and untimely dispatch, receipt and/or content of this e-mail.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

[Plplot-devel] Best git version for Windows?

[Alan W. Irwin]

To Jim, Phil, and Arjen:

On 2017-02-20 00:38-0500 Jim Dishaw wrote:

> I need your help to sort out git.  Long story short, I had a disk
corruption on the VM that I was doing my development work and had to
recover my work.  I manage to get my wingdi driver recovered from the
smoking heap.

@Jim:

My sympathies concerning your hardware troubles.  I am especially
sensitive to that issue because I just went through a hardware scare
myself (spent a lot of yesterday running hardware tests when I ran
into the *.pyc corruption issue).  But amazingly this 9-year-old
hardware (with an ASUS motherboard which might be the reason for this
longevity) still passes all hardware tests, and I have concluded (with
a fair amount of confidence) that the *.pyc corruption issue must be
due to some Python bug.  So I plan to keep using this hardware for
a while longer.

> Unfortunately, I appear to be having problems with the git
repository on SourceForge and I am not sure of the cause—I cannot even
clone from SourceForge.

@Jim, Phil, and Arjen:

I used the git SF server just this morning with no issues.  Also, for
the reasons discussed in README.developers you should avoid all gui
versions or "enhanced" versions of git (i.e., try to stick as much as
possible to the real thing).  Bearing those constraints in mind, that
file recommends  for Windows
users, but I just discovered from looking at that site that it has
been obsoleted and msysgit developers now recommend using the "Git for
Windows"  version of git instead.
(I confirmed from that website it considers itself light-weight
[check!] and it does have a command-line version [check!]).  So please
give the command-line version of that project a try, and let us know
whether it works well for you (which would allow us to recommend that
Windows version of git in our README.developers file).

Alan
__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel