git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kyle J. McKay" <mackyle@gmail.com>
To: Git mailing list <git@vger.kernel.org>
Cc: Michael Haggerty <mhagger@alum.mit.edu>
Subject: Potential GSOC microproject idea
Date: Sat, 8 Mar 2014 17:54:40 -0800	[thread overview]
Message-ID: <73E9BCA0-D55C-4751-A3C0-1CD21F296758@gmail.com> (raw)

On Mar 3, 2014, at 23:58, Michael Haggerty wrote:
> list
> regulars should FEEL ENCOURAGED to submit microprojects to add to the
> list.  (Either submit them as a pull request to the GitHub repository
> that contains the text [1] or to the mailing list with CC to me.)

Potential idea for a microproject:

Add a new config setting:

   user.allowImplicitIdentity
     Defaults to true.
     If user.name and GIT_COMMITTER_NAME are unset or user.email and
     GIT_COMMITTER_EMAIL and EMAIL are unset, an implicit value is
     substituted for one or both of user.name and user.email.  If
     an automatically generated value is used for both name and email
     a warning "Your name and email address were configured  
automatically..."
     is displayed.  If set to false, no or never, instead of a warning,
     an error is generated and the operation fails:

         *** Please tell me who you are.

         Run

           git config --global user.email "you@example.com"
           git config --global user.name "Your Name"

         to set your account's default identity.
         Omit --global to set the identity only in this repository.

         fatal: implicit user identity not allowed

     the advice portion can be suppressed by setting  
advice.implicitIdentity to false,
     but not the "fatal: implicit user identity not allowed" part.

Note that if "git config --system --bool user.allowImplicitIdentity  
false" is in effect, it should still be possible to clone (ref logs  
may be updated, but they should be allowed to use an implicit  
identity).  In other words user.allowImplicitIdentity=false should  
only inhibit writing any new commit/tag objects that need the current  
user's name and email when it has not been explicitly provided.

I'm not sure how micro this is.  :)  I do think the amount of code  
involved is rather small though.  Support for something like this has  
popped up on the list before.  Perhaps "user.allowAutomaticIdentity"  
and "advice.automaticIdentity" would be better config names.

--Kyle

             reply	other threads:[~2014-03-09  2:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-09  1:54 Kyle J. McKay [this message]
2014-03-10  8:35 ` Potential GSOC microproject idea Michael Haggerty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=73E9BCA0-D55C-4751-A3C0-1CD21F296758@gmail.com \
    --to=mackyle@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mhagger@alum.mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).