Re: Xcode 7.0.1 SIGSEV on Git push

2015-10-01 Thread Alex Zavatone
FWIW, I don't get the crash on 7.0 when trying to commit, but I do get a sheet stating "Couldn't communicate with a helper application". Not a problem using Xcode 6.4 to commit. So, I'd really like to never have to waste time playing QA on issues like this when I have multiple products to

Re: Xcode 7.0.1 SIGSEV on Git push

2015-10-01 Thread Dave
> On 1 Oct 2015, at 15:58, Alex Zavatone wrote: > > FWIW, I don't get the crash on 7.0 when trying to commit, but I do get a > sheet stating "Couldn't communicate with a helper application". > > Not a problem using Xcode 6.4 to commit. > > So, I'd really like to never have to

Re: Xcode 7.0.1 SIGSEV on Git push

2015-10-01 Thread Alex Zavatone
FYI, I just spent the time to download 7.0.1 again from the developer site, reinstalled it, made one change to a file and tried to commit to my local git repo. Instant SIGSEV all over again. The exact same crash as listed below. Joy. I'm going to try with 7.0 and see if I can actually use

Re: Xcode 7.0.1 SIGSEV on Git push

2015-10-01 Thread Jens Alfke
> On Oct 1, 2015, at 1:49 AM, Dave wrote: > > Totally and utterly agree, I always go into a cold sweat whenever something > horrid happens related to Git and when using XCode it happens all too often. On the other hand, the nice thing with Git is that you can always

Re: Xcode 7.0.1 SIGSEV on Git push

2015-10-01 Thread Jens Alfke
> On Oct 1, 2015, at 7:13 AM, Alex Zavatone wrote: > > Yeah, Jens, I know. Use the command line, I know, I know. No, use SourceTree! I very rarely commit from the command line. SourceTree is free, and a great complement to Xcode... Xcode is better at diffs and blame,

Re: Xcode 7.0.1 SIGSEV on Git push

2015-10-01 Thread Dave
> On 1 Oct 2015, at 16:37, Jens Alfke wrote: > On the other hand, the nice thing with Git is that you can always undo what > happened. The "git reflog" command is a lifesaver -- it lists a history of > all the latest HEAD revisions. By resetting to an earlier HEAD you can

Re: Xcode 7.0.1 SIGSEV on Git push

2015-10-01 Thread Roland King
> > Yeah, Jens, I know. Use the command line, I know, I know. > > Amazing. Utterly amazing. > Well it’s good advice. This isn’t your first post about how the SCM inside Xcode broke something, sometimes Xcode, sometimes the repository. So stop using it. You’ve posted about this multiple

Re: Xcode 7.0.1 SIGSEV on Git push

2015-10-01 Thread Dave
> On 30 Sep 2015, at 22:31, Jens Alfke wrote: > > >> On Sep 30, 2015, at 2:01 PM, Alex Zavatone > > wrote: >> >> Can't commit anything. Fun times. > > There’s this obscure command-line tool called “git”… ;-) Or GUI apps like >

Xcode 7.0.1 SIGSEV on Git push

2015-09-30 Thread Alex Zavatone
Mac OS 10.11 Xcode 7.0.1 com.apple.dt.Xcode.sourcecontrol.Git Just tested out my iOS 7/8 apps under Xcode 7.0.1, disabled bitcode so that they would let all targets would build and run on my iOS 7 and 8 devices. Updated the build settings as recommended which overwrote my custom entered info

Re: Xcode 7.0.1 SIGSEV on Git push

2015-09-30 Thread Jens Alfke
> On Sep 30, 2015, at 2:01 PM, Alex Zavatone wrote: > > Can't commit anything. Fun times. There’s this obscure command-line tool called “git”… ;-) Or GUI apps like SourceTree (free!) (Seriously, I _never_ commit or push anything from Xcode anymore. I’ve seen it do the wrong

Re: Xcode 7.0.1 SIGSEV on Git push

2015-09-30 Thread Alex Zavatone
On Sep 30, 2015, at 5:31 PM, Jens Alfke wrote: > >> On Sep 30, 2015, at 2:01 PM, Alex Zavatone wrote: >> >> Can't commit anything. Fun times. > > There’s this obscure command-line tool called “git”… ;-) Or GUI apps like > SourceTree (free!) Yeah, I though "or I could use the