for my part, I don't set user.email in my global .gitconfig because I've often committed with the wrong address. Leaving it undefined then gives you a warning when you commit. I then set the right local value and --amend --reset-author. Pretty sure our apache repo insists on apache.org addresses too.
B. On 28 February 2012 03:58, Paul Davis <[email protected]> wrote: > To be clear, Randall means to set the user.email and user.name setting > in the ./git/config file in your CouchDB clone. > > On Mon, Feb 27, 2012 at 8:32 PM, Adam Kocoloski <[email protected]> wrote: >> On Feb 27, 2012, at 8:53 PM, Randall Leeds wrote: >> >>> On Mon, Feb 27, 2012 at 16:22, Jason Smith <[email protected]> wrote: >>>> Quick question: >>>> >>>> Do you all have any strategies or techniques for committing under >>>> various identities? I would like CouchDB commits to be [email protected], >>>> but work projects, under different email addresses. >>>> >>>> This one is hard to google. It's tons of walkthroughs for identifying >>>> to a Git server (SSH key management, etc.). I'm just talking about the >>>> committer ID. >>>> >>>> All I've thought to do is make fresh clones and run git config >>>> user.email [email protected]. Then I guess I'll use that for working on >>>> couch, any commits that might one day go upstream. And I'll pull them >>>> in to other branches and forks? >>> >>> You needn't make a fresh clone to set your email address. I keep my >>> gmail in --global and my CouchDB repo as @apache.org. >> >> Ditto.
