Thanks for the detailed reply. Yes, I had posted on Stackoverflow once
I found a workable solution. Today was the first day that this original
(but doubled) posting of mine showed up, so hadn't replied here yet. I
posted my answer to a couple of threads I had found over there. For those
not inclined to browse over there, the short version is that I installed
the Xcode command line tools by themselves. That appears to have installed
git v 1.8.5. That version works fine on my machine.
I haven't messed with Homebrew at all. Yes, I had downloaded the most
recent installer from git-scm; it installed 1.9.2 in spite of the graphic
showing that it was 1.9.3.
On Monday, June 2, 2014 3:06:08 PM UTC-7, Thomas Ferris Nicolaisen wrote:
> On Friday, May 30, 2014 7:15:47 AM UTC+2, Justin Close wrote:
> There's often confusion when installing Git OS X, because Apple ships an
> older version of Git with OS X (or is it with XCode? Can't remember).
> In any case, you want to find out which Git is being used, and if it's the
> intended installation. To orient yourself, you have some commands:
> which git # what is the first git executable in your path
> git --version #what version is this pointing at, you'll want this to be
> 1.9.2 I suppose
> echo $PATH # what does the whole path look like
> Most people on OS X who want a fresh version of Git either install the one
> they download from git-scm.com - or they install it/build it using
> homebrew <http://brew.sh/>.
> I believe the git-scm.com installer will end up putting Git in
> /usr/local/git/bin/git, whereas default homebrew will put it in
> /usr/local/bin/git (I haven't got my mac here, so I can't guarantee this).
> I think the following happened: You downloaded and ran the git-scm.com
> installer, and something in your environment (OS X version, whatever is
> installed) ended up confusing the installer, and it got some things set up
> While this installer obviously gets a lot of exposure, I'm not sure if
> it's being so well-maintained (seeing how they are lagging a few minor
> versions behind the other installers) for the various upgrades Apple puts
> out there which accidentally breaks stuff. I'm sure people would be
> grateful if you would open a ticket in their project:
> I suspect most developers out there, myself included, just stick to using
> homebrew these days, as building for your own machine is usually the safest
> thing to do. But using homebrew and building Git still requires you to
> install the XCode command line tools.
> Hope this gives you some bearings. Note that I haven't researched this too
> heavily, it's just my feel of what things are like now. Sorry there's not
> an easier way.
> PS: Seems you did some cross posting on SO:
> http://stackoverflow.com/a/23964601 and
> http://stackoverflow.com/a/23964569 - including these for reference.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.