If it&#39;s an annotated tag, then yes. You can `git show` it just like any other object. If it&#39;s a lightweight tag, then I don&#39;t believe so. Just one of the reasons why you should always annotate the tags you&#39;re going to share.

You can use this command to show git tags with date, message and author email:

    git for-each-ref --format &#39;%(refname) %09 %(taggerdate) %(subject) %(taggeremail)&#39; refs/tags  --sort=taggerdate

This is the result of this command when I launch it on [Material-UI][1] project:

[![enter image description here][2]][2]


  [1]: https://github.com/mui-org/material-ui
  [2]: https://i.stack.imgur.com/np6T7.png

Yes.  
-&gt; git tag  
then for specific version

-&gt; git show  
[Refer to github guide](http://learn.github.com/p/tagging.htm)

I&#39;m trying to style the dropdown arrow of a `&lt;select&gt;` element with CSS only , it works perfectly in Chrome/Safari:

    select {
      -webkit-appearance: button;
      -webkit-border-radius: 2px;
      -webkit-box-shadow: 0px 1px 3px rgba(0, 0, 0, 0.1);
      -webkit-padding-end: 20px;
      -webkit-padding-start: 2px;
      -webkit-user-select: none;
      
      background-image: url(&#39;./select-arrow1.png&#39;) ;
      background-position: center right;
      background-repeat: no-repeat;
      border: 1px solid #AAA;
      margin: 0;
      padding-top: 2px;
      padding-bottom: 2px;
      width: 200px;
    }

Which renders beautifully [as seen here](http://i.imgur.com/bYl2X.jpg)

By that logic, the only thing I had to do to make it work in Firefox was to add all `-webkit-*` stuff as `-moz-*` :
    
    -moz-appearance: button;
    -moz-border-radius: 2px;
    -moz-box-shadow: 0px 1px 3px rgba(0, 0, 0, 0.1);
    -moz-padding-end: 20px;
    -moz-padding-start: 2px;
    -moz-user-select: none;
    

It works for 99%, the only problem is that the default dropdown arrow doesn&#39;t go away, and stays on top of the background image [as seen here](http://i.imgur.com/SQPXO.jpg)

It looks like `-moz-appearance: button;` does not work for a `&lt;select&gt;` element. Also `-moz-appearance: none;` has no effect to remove the default dropdown arrow.

So what is the correct value for `-moz-appearance` to remove the default dropdown arrow? 

Updates:
=======

**December 11, 2014**: **Stop inventing new hacks**. After 4 and a half years, `-moz-appearance:none` is starting to work since Firefox 35. Although `moz-appearance:button` is still broken, you don&#39;t need to use it anyway. [Here is a very basic working example.](http://jsfiddle.net/88rpe9ze/) 

**April 28, 2014**: The mentioned [css hack](//stackoverflow.com/questions/6787667/what-is-the-correct-moz-appearance-value-to-hide-dropdown-arrow-of-a-select#answer-18327666) worked for a couple of months but since the begining of April 2014 this bug is creeping back into Firefox 31.0.a1 Nightly on all platforms.




What is the correct &quot;-moz-appearance&quot; value to hide dropdown arrow of a &lt;select&gt; element

I have Go program that has a function defined. I also have a map that should have a key for each function. How can I do that?

I have tried this, but this doesn&#39;t work.
&lt;pre&gt;
func a(param string) {

}

m := map[string] func {
    &#39;a_func&#39;: a,
}

for key, value := range m {
   if key == &#39;a_func&#39; {
    value(param) 
   }
}
&lt;/pre&gt;

Go map of functions

Commits obviously have an author associated with them; but is it possible to find out which user created a tag on a Git repository?


Is it possible to find out who created a tag in Git?

<p>Commits obviously have an author associated with them; but is it possible to find out which user created a tag on a Git repository?</p>


It&#39;s very common to have at least one configuration file in any project. Every time I share project with `git`, I have the same problem with:

 - sensitive information (each developer have different DB passwords etc)
 - task specific information (when developer works on certain task where one needs to change some settings)

Obviously, configs have to be ignored somehow to prevent developer specific data to flood main repository. Now there are several ways I used to use, each with some flaws:

 - `.gitignore` the config files
     - the most basic way
     - when developer clones repo, config file is missing and one has to find out where configs were recreate them
 - config file isn&#39;t ignored. It contains some dummy info and each developer either untracks and puts it to his `.git/info/exclude` or set `git update-index --assume-unchanged ...` to the file
     - files are available for anyone who clones repo
     - it contains advanced techniques which could confuse people that work with git for the first time
     - when someone commits config files by accident, it won&#39;t allow people to pull/fetch (as excludes don&#39;t work the same way as `.gitignore`)
 - distribute config files suffixed with, for example, `_original` while having the real files in `.gitignore`. Each developer then renames files to real names
     - files are available for anyone who clones repo
     - one has to search for all configs throughout application and rename them

Are there any other, possibly, better ways to handle this? I suspect I&#39;m missing something, some plugin at least.

What&#39;s the easiest way to deal with project configuration files?

**SITUATION:**

I have a python library, which is controlled by git, and bundled with distutils/setuptools. And I want to automatically generate version number based on git tags, both for `setup.py sdist` and alike commands, and for the library itself.

For the first task I can use `git describe` or alike solutions (see  https://stackoverflow.com/questions/2058802/how-can-i-get-the-version-defined-in-setup-py-setuptools-in-my-package).

And when, for example, I am in a tag &#39;0.1&#39; and call for &#39;setup.py sdist&#39;, I get &#39;mylib-0.1.tar.gz&#39;; or &#39;mylib-0.1-3-abcd.tar.gz&#39; if I altered the code after tagging. This is fine.

**THE PROBLEM IS:**

The problem comes when I want to have this version number available for the library itself, so it could send it in User-Agent HTTP header as &#39;mylib/0.1-3-adcd&#39;.

If I add `setup.py version` command as in https://stackoverflow.com/questions/2058802/how-can-i-get-the-version-defined-in-setup-py-setuptools-in-my-package, then this version.py is generated AFTER the tag is made, since it uses the tag as a value. But in this case I need to make one more commit after the version tag is made to make the code consistent. Which, in turns, requires a new tag for further bundling.

**THE QUESTION IS:**

How to break this circle of dependencies (generate-commit-tag-generate-commit-tag-...)?


Automatic version number both in setup.py (setuptools) AND source code?

how do i revert all my files on my local copy back to a certain commit?


    commit 4a155e5b3b4548f5f8139b5210b9bb477fa549de
    Author: John Doe &lt;Doe.John.10@gmail.com&gt;
    Date:   Thu Jul 21 20:51:38 2011 -0500


This is the commit i&#39;d like to revert back to. any help would be a lifesaver!



git revert back to certain commit

I have a structure similar to the following: 

    /root/
    /root/data/
    /root/data/script.php
    /root/data/some.json
    /root/data/feature/one.json
    /root/data/feature/two.json
    /root/data/other-feature/one.json
    /root/data/other-feature/important-script.php

I&#39;d like git to ignore *any* `.json` files under the &#39;/data/...&#39; path, but &#39;/data/&#39; sometimes contains sub-directories. 

My understanding is that a simple `data/*.json` in gitignore will only match one directory, as the `*` doesn&#39;t match `/`, as stated at http://git-scm.com/docs/gitignore, &quot;Pattern Format&quot;, bullet #6: 

&gt;Otherwise, git treats the pattern as a shell glob suitable for consumption by fnmatch(3) with the FNM_PATHNAME flag: wildcards in the pattern will not match a / in the pathname. For example, &quot;Documentation/*.html&quot; matches &quot;Documentation/git.html&quot; but not &quot;Documentation/ppc/ppc.html&quot; or &quot;tools/perf/Documentation/perf.html&quot;.

Is there a simple way to do this, or do I need to actively add gitignore files in each sub-directory, explicitly?


Git-ignore certain files in sub-directories, but not all

I am wondering if there is a way to view a push date associated with each commit in the git log.  If that is not possible, is there a way to see all the commits under a certain push.

I writing a program that needs to keep track of the commits as they are pushed.  Because the git log is ordered by the commit date, not the push date, I am not able to see the most recent commits that are pushed. For example, if a user commits to his local repository 2 days before he pushes to the master, that commit will be placed behind 2 days of other commits in the master repository log.

Content Type	Original Author	Original Content on Stackoverflow
Question	Smashery	View Question on Stackoverflow
Solution 1 - Git	Lily Ballard	View Answer on Stackoverflow
Solution 2 - Git	Ala Eddine JEBALI	View Answer on Stackoverflow
Solution 3 - Git	insomiac	View Answer on Stackoverflow

Is it possible to find out who created a tag in Git?

Git Problem Overview

Git Solutions

Solution 1 - Git

Solution 2 - Git

Solution 3 - Git

Go map of functions

What is the correct "-moz-appearance" value to hide dropdown arrow of a <select> element

Attributions