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 ship. Yes, there is the terminal, but I enjoy 
a good, stable and functional GUI for these trivial things such as source code 
control.

If anyone can suggest a top notch professional Git client for iOS projects, 
I'll purchase it instantly.  I don't have the time to waste dealing with 
crashes in core functionality of the IDE.  I'll pay for a professional solution 
immediately.

Thanks for any suggestions on this front.

- Alex Zavatone


On Oct 1, 2015, at 10:13 AM, Alex Zavatone wrote:

> 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 the product to commit 
> changes without crashing and let the list know if that works.
> 
> Yeah, Jens, I know.  Use the command line, I know, I know.
> 
> Amazing.  Utterly amazing.
> 
> 
> On Sep 30, 2015, at 5:01 PM, Alex Zavatone wrote:
> 
>> Yeah, I'm checking to see if I need the new command line tools right now.
>> 
>> Can't commit anything.  Fun times.
>> 
>> FYI, if you use external libs, and your app doesn't build, go to build 
>> settings and disable bitcode.  It appears that the lib checking is a little 
>> more rigorous and it appears that one of our libs was built for a version of 
>> iOS that is "too new for the target OS".  We still support iOS 7 and the lib 
>> was built for iOS 8 but previously, Xcode 6.4 didn't complain about that.
>> 
>> Also, for iOS if you entered custom information in your target app 
>> info.plist files, it's likely that some of that data will be overwritten.  
>> 
>> OK.  Just rebooted, installed the command line tools for 10.11 for Xcode 7, 
>> same crash on commit.
>> 
>> Hilariously, I can reopen Xcode 6.4, commit and push to my local and remote 
>> repo, but um, well.
>> 
>> Anyway.
>> 
>> It appears I didn't include the thread that crashed, but here it is.
>> 
>> Thread 1 Crashed:: Dispatch queue: com.apple.NSXPCConnection.user.2356
>> 0   com.apple.dt.Xcode.sourcecontrol.Git 0x0001099481ff 0x10993a000 
>> + 57855
>> 1   com.apple.dt.Xcode.sourcecontrol.Git 0x0001099472b0 0x10993a000 
>> + 53936
>> 2   com.apple.CoreFoundation 0x7fff96a2c8cc invoking_ + 140
>> 3   com.apple.CoreFoundation 0x7fff96a2c75e -[NSInvocation 
>> invoke] + 286
>> 4   com.apple.Foundation 0x7fff8e6ab0d8 
>> NSXPCCONNECTION_IS_CALLING_OUT_TO_EXPORTED_OBJECT + 17
>> 5   com.apple.Foundation 0x7fff8e6aaa42 -[NSXPCConnection 
>> _decodeAndInvokeMessageWithData:] + 1123
>> 6   com.apple.Foundation 0x7fff8e6aa510 message_handler + 705
>> 7   libxpc.dylib 0x7fff95058986 
>> _xpc_connection_call_event_handler + 35
>> 8   libxpc.dylib 0x7fff950571ff 
>> _xpc_connection_mach_event + 2198
>> 9   libdispatch.dylib0x7fff8f5c95a4 
>> _dispatch_client_callout4 + 9
>> 10  libdispatch.dylib0x7fff8f5c9a14 
>> _dispatch_mach_msg_invoke + 555
>> 11  libdispatch.dylib0x7fff8f5c6248 
>> _dispatch_queue_drain + 1207
>> 12  libdispatch.dylib0x7fff8f5c836d 
>> _dispatch_mach_invoke + 735
>> 13  libdispatch.dylib0x7fff8f5c6248 
>> _dispatch_queue_drain + 1207
>> 14  libdispatch.dylib0x7fff8f5cc6c9 
>> _dispatch_queue_invoke + 549
>> 15  libdispatch.dylib0x7fff8f5c1453 
>> _dispatch_client_callout + 8
>> 16  libdispatch.dylib0x7fff8f5c52e3 
>> _dispatch_root_queue_drain + 1890
>> 17  libdispatch.dylib0x7fff8f5c4b48 
>> _dispatch_worker_thread3 + 91
>> 18  libsystem_pthread.dylib  0x7fff9500d4f2 _pthread_wqthread + 
>> 1129
>> 19  libsystem_pthread.dylib  0x7fff9500b375 start_wqthread + 13
>> 
>> 
>> 
>> On Sep 30, 2015, at 4:45 PM, Tony Scaminaci wrote:
>> 
>>> Guess I'll hold off downloading 7.01...
>>> 
>>> 
>>> 
>>> On Wednesday, September 30, 2015 3:43 PM, Alex Zavatone  
>>> wrote:
>>> 
>>> 
>>> 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 in the info plists.  Went to commit and push to our remote git repo 
>>> and checked the "push to remote" checkbox and clicked OK.
>>> 
>>> Instant SIGSEV

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 waste time playing QA on issues like 
> this when I have multiple products to ship. Yes, there is the terminal, but I 
> enjoy a good, stable and functional GUI for these trivial things such as 
> source code control.
> 
> If anyone can suggest a top notch professional Git client for iOS projects, 
> I'll purchase it instantly.  I don't have the time to waste dealing with 
> crashes in core functionality of the IDE.  I'll pay for a professional 
> solution immediately.

Try out GitTower - I really rate it and it’s on a 30 day evaluation so you 
really have nothing to lose:

http://www.git-tower.com

Hope it helps.

Cheers
Dave





smime.p7s
Description: S/MIME cryptographic signature
 ___
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list  (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

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 the product to commit 
changes without crashing and let the list know if that works.

Yeah, Jens, I know.  Use the command line, I know, I know.

Amazing.  Utterly amazing.


On Sep 30, 2015, at 5:01 PM, Alex Zavatone wrote:

> Yeah, I'm checking to see if I need the new command line tools right now.
> 
> Can't commit anything.  Fun times.
> 
> FYI, if you use external libs, and your app doesn't build, go to build 
> settings and disable bitcode.  It appears that the lib checking is a little 
> more rigorous and it appears that one of our libs was built for a version of 
> iOS that is "too new for the target OS".  We still support iOS 7 and the lib 
> was built for iOS 8 but previously, Xcode 6.4 didn't complain about that.
> 
> Also, for iOS if you entered custom information in your target app info.plist 
> files, it's likely that some of that data will be overwritten.  
> 
> OK.  Just rebooted, installed the command line tools for 10.11 for Xcode 7, 
> same crash on commit.
> 
> Hilariously, I can reopen Xcode 6.4, commit and push to my local and remote 
> repo, but um, well.
> 
> Anyway.
> 
> It appears I didn't include the thread that crashed, but here it is.
> 
> Thread 1 Crashed:: Dispatch queue: com.apple.NSXPCConnection.user.2356
> 0   com.apple.dt.Xcode.sourcecontrol.Git  0x0001099481ff 0x10993a000 
> + 57855
> 1   com.apple.dt.Xcode.sourcecontrol.Git  0x0001099472b0 0x10993a000 
> + 53936
> 2   com.apple.CoreFoundation  0x7fff96a2c8cc invoking_ + 140
> 3   com.apple.CoreFoundation  0x7fff96a2c75e -[NSInvocation 
> invoke] + 286
> 4   com.apple.Foundation  0x7fff8e6ab0d8 
> NSXPCCONNECTION_IS_CALLING_OUT_TO_EXPORTED_OBJECT + 17
> 5   com.apple.Foundation  0x7fff8e6aaa42 -[NSXPCConnection 
> _decodeAndInvokeMessageWithData:] + 1123
> 6   com.apple.Foundation  0x7fff8e6aa510 message_handler + 705
> 7   libxpc.dylib  0x7fff95058986 
> _xpc_connection_call_event_handler + 35
> 8   libxpc.dylib  0x7fff950571ff 
> _xpc_connection_mach_event + 2198
> 9   libdispatch.dylib 0x7fff8f5c95a4 
> _dispatch_client_callout4 + 9
> 10  libdispatch.dylib 0x7fff8f5c9a14 
> _dispatch_mach_msg_invoke + 555
> 11  libdispatch.dylib 0x7fff8f5c6248 
> _dispatch_queue_drain + 1207
> 12  libdispatch.dylib 0x7fff8f5c836d 
> _dispatch_mach_invoke + 735
> 13  libdispatch.dylib 0x7fff8f5c6248 
> _dispatch_queue_drain + 1207
> 14  libdispatch.dylib 0x7fff8f5cc6c9 
> _dispatch_queue_invoke + 549
> 15  libdispatch.dylib 0x7fff8f5c1453 
> _dispatch_client_callout + 8
> 16  libdispatch.dylib 0x7fff8f5c52e3 
> _dispatch_root_queue_drain + 1890
> 17  libdispatch.dylib 0x7fff8f5c4b48 
> _dispatch_worker_thread3 + 91
> 18  libsystem_pthread.dylib   0x7fff9500d4f2 _pthread_wqthread + 
> 1129
> 19  libsystem_pthread.dylib   0x7fff9500b375 start_wqthread + 13
> 
> 
> 
> On Sep 30, 2015, at 4:45 PM, Tony Scaminaci wrote:
> 
>> Guess I'll hold off downloading 7.01...
>> 
>> 
>> 
>> On Wednesday, September 30, 2015 3:43 PM, Alex Zavatone  wrote:
>> 
>> 
>> 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 in the info plists.  Went to commit and push to our remote git repo and 
>> checked the "push to remote" checkbox and clicked OK.
>> 
>> Instant SIGSEV crash.
>> 
>> Process:  com.apple.dt.Xcode.sourcecontrol.Git [70976]
>> Path:  
>> /Applications/Xcode.app/Contents/SharedFrameworks/DVTSourceControl.framework/Versions/A/XPCServices/com.apple.dt.Xcode.sourcecontrol.Git.xpc/Contents/MacOS/com.apple.dt.Xcode.sourcecontrol.Git
>> Identifier:com.apple.dt.Xcode.sourcecontrol.Git
>> Version:  1.0 (1)
>> Code Type:X86-64 (Native)
>> Parent Process:??? [1]
>> Responsible:  Xcode [41168]
>> User ID:  501
>> 
>> Date/Time:2015-09-30 16:32:29.806 -0400
>> OS Version:Mac OS X 10.11 (15A282b)
>> Report Version:11
>> Anonymous UUID:9187397F-46CF-9EA7-B1B6-6C7445ABD143
>> 
>> Sleep/Wake UUID:  AC6A45A8-6E27-4B5B-BF97-3D19FFA2A719
>> 
>> Time Awake Since Boot: 5 seconds
>> Time Since Wake:  2500 seconds
>> 
>>

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 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 effectively 
rewind time on the current branch. (Of course, once you've pushed your mistakes 
to a server, things get messier...)

--Jens
 ___
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list  (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

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, 
SourceTree is better at everything else.

--Jens
 ___
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list  (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

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 
> effectively rewind time on the current branch. (Of course, once you've pushed 
> your mistakes to a server, things get messier…)
> 

The ultimate in diff tools is "Araxis Merge Pro” IMO, it’s a tad expensive but 
the best of it’s kind I’ve used:

http://www.araxis.com/merge/index.en

Cheers
Dave



smime.p7s
Description: S/MIME cryptographic signature
 ___
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list  (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

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 times over multiple months or years. 
Xcode’s SCM isn’t very good, feel free to file bugs against it to make it 
better but find a workflow for your business which you can rely on. You say “I 
know, I know” and perhaps you do know but it seems you keep hoping the next 
time’s the charm. 

I use Xcode to write, compile and debug code
I use Packages to make packages
I use git command line or Sourcetree to deal with SCM
I use Crossworks for all my ARM development
I use Dash to peruse documentation
I use KiCad to make circuit boards
I use vim generally because I’m ancient and my fingers have learned where the 
keys are

Horses for courses. I don’t have one integrated Swiss Army knife to do 
everything but I’ve never found that switching between applications to do tasks 
was any harder than switching windows in one app and I get a tool someone has 
lovingly written to do one exact thing. That option is a CMD-Tab away. 

It’s nice that Xcode integrates with git enough to put an ‘M’ against modified 
files, for everything else, there’s a better tool. 

I do appreciate your agony with Xcode’s SCM but after this long it’s not 
unreasonable to suggest you have stoically banged your head against the wall 
for long enough. This is SCM, it’s what you do when you’re not writing code, 
there’s too many options available to not find a better solution for your 
company.  



 ___
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list  (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

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 
> SourceTree (free!)
> 
> (Seriously, I _never_ commit or push anything from Xcode anymore. I’ve seen 
> it do the wrong thing too many times, including committing changes in other 
> repositories that I didn’t tell it to commit to … I think this is because of 
> the truly screwy way it deals with submodules. I’ll use Xcode for diffs, but 
> that’s it.)
> 
> —Jens

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.

I use GitTower and would recommend it to anyone that needs a good Git Client, 
there’s a 30 day evaluation so you can try it out for free if you want to.

All the Best
Dave




smime.p7s
Description: S/MIME cryptographic signature
 ___
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list  (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

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 in the info plists.  Went to commit and push to our remote git repo and 
checked the "push to remote" checkbox and clicked OK.

Instant SIGSEV crash.

Process:   com.apple.dt.Xcode.sourcecontrol.Git [70976]
Path:  
/Applications/Xcode.app/Contents/SharedFrameworks/DVTSourceControl.framework/Versions/A/XPCServices/com.apple.dt.Xcode.sourcecontrol.Git.xpc/Contents/MacOS/com.apple.dt.Xcode.sourcecontrol.Git
Identifier:com.apple.dt.Xcode.sourcecontrol.Git
Version:   1.0 (1)
Code Type: X86-64 (Native)
Parent Process:??? [1]
Responsible:   Xcode [41168]
User ID:   501

Date/Time: 2015-09-30 16:32:29.806 -0400
OS Version:Mac OS X 10.11 (15A282b)
Report Version:11
Anonymous UUID:9187397F-46CF-9EA7-B1B6-6C7445ABD143

Sleep/Wake UUID:   AC6A45A8-6E27-4B5B-BF97-3D19FFA2A719

Time Awake Since Boot: 5 seconds
Time Since Wake:   2500 seconds

System Integrity Protection: enabled

Crashed Thread:4  Dispatch queue: com.apple.NSXPCConnection.user.41168

Exception Type:EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   KERN_INVALID_ADDRESS at 0x
Exception Note:EXC_CORPSE_NOTIFY

VM Regions Near 0:
--> 
__TEXT 0001018d-0001018f [  128K] r-x/rwx 
SM=COW  
/Applications/Xcode.app/Contents/SharedFrameworks/DVTSourceControl.framework/Versions/A/XPCServices/com.apple.dt.Xcode.sourcecontrol.Git.xpc/Contents/MacOS/com.apple.dt.Xcode.sourcecontrol.Git

Thread 0:
0   libsystem_kernel.dylib  0x7fff8cd482ca 
__semwait_signal_nocancel + 10
1   libsystem_c.dylib   0x7fff98087f12 nanosleep$NOCANCEL + 
188
2   libsystem_c.dylib   0x7fff980b0114 sleep$NOCANCEL + 42
3   libdispatch.dylib   0x7fff8bfe0755 
_dispatch_queue_cleanup2 + 140
4   libsystem_pthread.dylib 0x7fff98c5e3f1 _pthread_tsd_cleanup 
+ 555
5   libsystem_pthread.dylib 0x7fff98c5df78 _pthread_exit + 117
6   libsystem_pthread.dylib 0x7fff98c5ec22 pthread_exit + 30
7   libdispatch.dylib   0x7fff8bfe06ab dispatch_main + 43
8   libxpc.dylib0x7fff98063473 _xpc_objc_main + 666
9   libxpc.dylib0x7fff98061f1e xpc_main + 494
10  com.apple.Foundation0x7fff8a8651e3 -[NSXPCListener 
resume] + 160
11  com.apple.dt.Xcode.sourcecontrol.Git0x0001018d1918 main + 107
12  libdyld.dylib   0x7fff864d45ad start + 1



 ___
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list  (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

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 thing too many times, including committing changes in other 
repositories that I didn’t tell it to commit to … I think this is because of 
the truly screwy way it deals with submodules. I’ll use Xcode for diffs, but 
that’s it.)

—Jens ___
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list  (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

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 terminal" only after I realized I launched 
the previous version of Xcode to be able to commit.

Just ran into the screwed up Check Out window as well where the paths to the 
repos have line wraps.  I really with the Xcode team would STOP screwing with 
the interface once they got it to work.  We need less crap flying all over the 
place and more of a dev tool that actually does its job.

I remember when our team found out that those little disclosure triangles had 
been removed from the items in the Inspector panels that now look like plain 
old text.  People (myself included) wasted 1/2 an hour trying to find the 
options that were so easy to see before BECAUSE THERE WAS UI THAT SHOWED US 
THAT THE ELEMENT WAS CLICKABLE.

This minimalist UI needs to die in a fire.

Anyway, it looks like I may actually have a screwed up version of Xcode 
downloaded from the developer site even though it passed all checks on the 
install.

I hope it's as simple as that.

> (Seriously, I _never_ commit or push anything from Xcode anymore. I’ve seen 
> it do the wrong thing too many times, including committing changes in other 
> repositories that I didn’t tell it to commit to … I think this is because of 
> the truly screwy way it deals with submodules. I’ll use Xcode for diffs, but 
> that’s it.)
> 
> —Jens

 ___
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list  (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to arch...@mail-archive.com