StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9931009
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-03-29T18:12:30.330
FavoriteCount
0
LastActivityDate
2012-03-30T08:15:59.237
LastEditDate
2012-03-30T08:15:59.237
LastEditorUserId
92837
OwnerUserId
451066
ParentId
9926186
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Have you looked at git describe? <a href="http://linux.die.net/man/1/git-describe" rel="nofollow">http://linux.die.net/man/1/git-describe</a> I use this output for a number of different projects. It will give you the closest tag in the past, the number of commits since the tag, and a few characters from the hash. Here is an example from the manpage: v1.0.4-14-g2414721 In this example, the parts are: <ul> <li>the tag is 'v1.0.4'</li> <li>there have been 14 commits after the tag on this branch</li> <li>the hash prefix is 2414721</li> </ul> If the last commit is tagged, you'll get only the tag name: v1.0.4 There are lots of useful options, but the two that are most important to my projects are: <blockquote> <code>--tags:</code> I use lightweight, unsigned tags which it doesn't pick up by default. <code>--match:</code> If you have different types of tags but only want to match those that start with 'v'. </blockquote> From a process point of view, what I do for serious projects is to also: <ol> <li>Change the version and count to an rc or beta format: <pre><code>tag v1.2-14 --> `1.3-rc14` or `1.3-beta14` </code></pre> You can't be building 1.2 since it is in the past, so it must be the 14th build of the next version which is 1.3.</li> <li>Prepend the branch name if it is a special branch (not master, etc.) For example, "v1.2-14" on branch "featurex" would produce: <pre><code>featurex-1.3-rc14 </code></pre></li> <li>Append <code>-modified</code> or `-unsupported" if the build doesn't have everything checked in. This is your clue that you will never be able to reproduce it. <pre><code> featurex-1.3-rc14-unsupported </code></pre></li> <li>Store the hash on the end or on the next line in logs or about screens. I normally put the full hash into logs and such, but the smaller prefix is common: <code>featurex-1.3-rc14 (2414721)</code> This works nicely with my workflow. When I merge the feature into a release branch, the prefix goes away: <code>1.3-rc14 (2414721)</code></li> </ol> When testing is complete and the version is tagged, the rc goes away: <code>1.3 (2414721)</code>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow can I add git hashes to my Eclipse RCP application About page?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USSathya
UserOwnerUserId
1. USmkleehammer
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.