Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add follow up your last commit #139

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dmlemos
Copy link
Contributor

@dmlemos dmlemos commented Feb 23, 2017

When you leave for the day and come back next day without much clue in what you did the day before. Or when you finish something and don't come back to it for a few weeks.

This command lists your last commit, which should help knowing what you did 馃槃

@hemanth
Copy link
Contributor

hemanth commented Feb 23, 2017

Is it a little too much 馃?

@Thanood
Copy link

Thanood commented Feb 23, 2017

I love it. 馃槀

@dmlemos
Copy link
Contributor Author

dmlemos commented Feb 23, 2017

Discovered this repo recently so I am just giving my contributions. Mostly going through my aliases. Hope it helps other people as well.

@hemanth
Copy link
Contributor

hemanth commented Feb 24, 2017

Let us wait for some more upvotes?

aliases at times can get too messy.

@goldie-lin
Copy link

goldie-lin commented Mar 28, 2017

I thought the option--global in git config --global user.email was a typo, should it be --get?

@dmlemos
Copy link
Contributor Author

dmlemos commented Mar 29, 2017

--global is a parameter referencing the location of the config file in the disk.

The default action for the command is to do a get, hence why it is omitted. However, the default config file location is global. Hence git config --get user.email also works.

from git config help

Config file location
    --global              use global config file
    --system              use system config file
    --local               use repository config file

@goldie-lin
Copy link

goldie-lin commented Mar 29, 2017

In my opinion, --get is more generic than --global, --system, and --local options; since I had few git repositories which setup user.name and user.email locally. Just my two cents.

Could I know why you prefer --global rather than others?

By the way, I set my global user.name and user.email in ~/.config/git/config ~/.config/git/config.local instead of ~/.gitconfig, and I'm just aware of that --global didn't work for me. It seems that --global option only works for ~/.gitconfig and ~/.config/git/config, not ~/.config/git/config ~/.config/git/config.local, maybe it's a bug of git.

Updated:

I found why my setup not work with --global. I did not save user.name and user.email in ~/.config/git/config, actually I saved it in ~/.config/git/config.local which it will be included from ~/.config/git/config by adding a git config --global include.path '~/.config/git/config.local' in ~/.config/git/config.

@goldie-lin
Copy link

Updated: I found why my setup not work with --global, hope you won't mind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants