• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: A different git problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A different git problem


  • Subject: Re: A different git problem
  • From: Roland King <email@hidden>
  • Date: Sat, 03 Oct 2015 10:38:25 +0800

> On 3 Oct 2015, at 09:40, John Brownie <email@hidden> wrote:
>
> On 2/10/2015 8:57, John Brownie wrote:
>> I checked the .gitconfig, and it has the correct information, but Xcode still gives me the error message, even after restarting Xcode. Is it caching the non-values? Rather annoying to do what it says and still have the same problem!
>
> After restarting the computer, I still have the same issue. I guess I'll work with SourceTree, which does work for me.


Possibly Xcode only just started caring about username and email and yours were always like this. That message looks to me like a generic .gitconfig was set up in a directory somewhere.

Try this - go somewhere which doesn’t have a git repository at all, like /tmp, in a terminal window, type

	git config user.email
	git config user.name

That should show you the globally configured email and name. If they are right then you probably have another .gitconfig in the actual project or somewhere between it and your home directory. If you go to the directory of the project you’re having issues with and type the same commands, do you get the same thing? If you get the myname@mymachinename.(none) then that’s coming from a .gitconfig somewhere between your project directory and your home directory. Or do the brute force approach and, from your home directory run

	find . -name .gitconfig -ls

it won’t be quick, but it will hunt out every git config file and you can go look at them.

If none of those things is the case, then it seems Xcode has SCM issues again.

I also would say that using SourceTree is a better plan anyway and it’s worth learning to drive git from the command line which is what I do most of the time but it’s worth figuring out where Xcode is reading this stuff from.
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


  • Follow-Ups:
    • Re: A different git problem
      • From: John Brownie <email@hidden>
    • Re: A different git problem
      • From: Roland King <email@hidden>
References: 
 >A different git problem (From: John Brownie <email@hidden>)
 >Re: A different git problem (From: Jens Alfke <email@hidden>)
 >Re: A different git problem (From: John Brownie <email@hidden>)
 >Re: A different git problem (From: John Brownie <email@hidden>)

  • Prev by Date: Re: A different git problem
  • Next by Date: Re: A different git problem
  • Previous by thread: Re: A different git problem
  • Next by thread: Re: A different git problem
  • Index(es):
    • Date
    • Thread