From: "Jakub Narębski" <jnareb@gmail.com>
To: Pranit Bauva <pranit.bauva@gmail.com>,
Yash Jain <yashjain.lnm@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Reporting Bug in Git Version Control System
Date: Mon, 31 Oct 2016 17:09:47 +0100 [thread overview]
Message-ID: <fb358e96-02e3-e162-94a6-7cf20ee3f7cf@gmail.com> (raw)
In-Reply-To: <CAFZEwPNB1PX_NOaYzKr+rUKvbC9s5A1G58v5aS=sGdzPVsv4ww@mail.gmail.com>
W dniu 25.10.2016 o 10:51, Pranit Bauva pisze:
> Hey Yash,
>
> Junio has explained the problem very well. Since you seem to be a
> beginner (guessing purely by your email) I will tell you how to fix
> it.
>
> Remember when you would have first installed git, you would have done
> something like `git config --global user.name <what ever name>` and
> `git config --global user.email <what ever email>`, it gets
> permanently stored in the git configuration file (~/.gitconfig). Now
> all the commits in git are made with this name and email. If you want
> to change this, again run the above commands with your new name and
> email. After that commits will be done with a different name and
> email. Hope this helps! :)
First, per user Git configuration doesn't necessarily go into ~/.gitconfig;
it could be in ~/.config/git/config
Second, you can configure user.email and user.name with `git config` or
`git config --local`. The information would go into .git/config for
specific repository. This might be a better solution if you want
different settings for different repositories.
--
Jakub Narębski
prev parent reply other threads:[~2016-10-31 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 14:28 Reporting Bug in Git Version Control System Yash Jain
2016-10-24 18:23 ` Stefan Beller
2016-10-24 18:32 ` Junio C Hamano
2016-10-24 21:14 ` Junio C Hamano
2016-10-25 8:51 ` Pranit Bauva
2016-10-31 16:09 ` Jakub Narębski [this message]
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=fb358e96-02e3-e162-94a6-7cf20ee3f7cf@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=pranit.bauva@gmail.com \
--cc=yashjain.lnm@gmail.com \
/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).