Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The thing you have you to understand about git is that branches are essentially merely commit bookmarks. The fact that you were on the <code>foo</code> branch when you made the <code>0deadbeef</code> commit is immaterial to the commit itself; the branch is not part of its identity.</p> <p>(Mercurial bakes the branch name into the commit. <a href="http://www.rockstarprogrammer.org/post/2008/apr/06/differences-between-mercurial-and-git/" rel="noreferrer">In a variety of ways, this is inferior, as Dustin Sallings explains</a>.)</p> <p>Even assuming that <code>git describe</code> would just use the currently checked out branch – if you have a mergy history, there could be multiple paths leading to the same most recent tagged commit that <code>git describe</code> would use. So there isn’t even necessarily any <em>one</em> branch.</p> <p>Another note: you may object that even if “3rd commit from tag X” is ambiguous in the general case, <code>git describe</code> could just look at the graph and figure out whether it <em>is</em> ambiguous and if not, leave out the hash. However, there is nothing stopping anyone starting a branch on top of that tag at a later time – so then your <code>describe</code> string would become ambiguous <em>retrospectively</em>.</p> <p>Bottom line is that the <strong>only</strong> unambiguous identifier of a commit is its hash. So that must be in there. What <code>git describe</code> does is add some <em>redundant</em> (and in case of the commit number, ambiguous) information that makes the description more useful to the kind of spatial/relational comprehension that humans orient themselves with, within the confines of the Git model.</p>
    singulars
    1. This table or related slice is empty.
    1. PODeriving application build version from `git describe` - how to get a relatively straightforward string?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAristotle Pagaltzis
    1. USAristotle Pagaltzis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODeriving application build version from `git describe` - how to get a relatively straightforward string?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYes, I have realized this property of branches now. With it, it would be ambigous to specify a branch indeed.
      singulars
      1. PO
      1. USamn
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload