From dev-return-21140-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Tue Feb 28 01:54:07 2012 Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3D6469FBC for ; Tue, 28 Feb 2012 01:54:07 +0000 (UTC) Received: (qmail 2683 invoked by uid 500); 28 Feb 2012 01:54:06 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 2647 invoked by uid 500); 28 Feb 2012 01:54:06 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 2639 invoked by uid 99); 28 Feb 2012 01:54:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Feb 2012 01:54:06 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of randall.leeds@gmail.com designates 209.85.210.52 as permitted sender) Received: from [209.85.210.52] (HELO mail-pz0-f52.google.com) (209.85.210.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Feb 2012 01:54:00 +0000 Received: by dado14 with SMTP id o14so7784308dad.11 for ; Mon, 27 Feb 2012 17:53:39 -0800 (PST) Received-SPF: pass (google.com: domain of randall.leeds@gmail.com designates 10.68.213.130 as permitted sender) client-ip=10.68.213.130; Authentication-Results: mr.google.com; spf=pass (google.com: domain of randall.leeds@gmail.com designates 10.68.213.130 as permitted sender) smtp.mail=randall.leeds@gmail.com; dkim=pass header.i=randall.leeds@gmail.com Received: from mr.google.com ([10.68.213.130]) by 10.68.213.130 with SMTP id ns2mr47680075pbc.10.1330394019435 (num_hops = 1); Mon, 27 Feb 2012 17:53:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=/Lwh2FanzLr2jRGyJGdyI1R3BIsCaY4iGBvRY3n1Buw=; b=GosgDtLgWleAsoW3Kz3BAghfN0bn4MgCSnf9llbQZfDA32Mg/tE8IP+Wplrxe68TVS B/VYdY414qiUpOIrCIL6lRn+QmsVglMRtHjzkbNKHyL596zH45muba/e8XrZhC44pimI p91XiSnSIaJjv739MKXwX7TxRvV8Iq9X7AHtw= MIME-Version: 1.0 Received: by 10.68.213.130 with SMTP id ns2mr40196115pbc.10.1330394019382; Mon, 27 Feb 2012 17:53:39 -0800 (PST) Received: by 10.68.2.197 with HTTP; Mon, 27 Feb 2012 17:53:39 -0800 (PST) In-Reply-To: References: Date: Mon, 27 Feb 2012 17:53:39 -0800 Message-ID: Subject: Re: Managing Git identities? From: Randall Leeds To: dev@couchdb.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Feb 27, 2012 at 16:22, Jason Smith wrote: > Quick question: > > Do you all have any strategies or techniques for committing under > various identities? I would like CouchDB commits to be jhs@apache.org, > 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 jhs@apache.org. 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. > > Is that what y'all are doing? > > -- > Iris Couch