Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><a href="https://stackoverflow.com/users/305973/robinst">robinst</a> mentions in the comments:</p> <blockquote> <p>This was simply a bug in EGit and happened only with annotated tags, please see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=417655" rel="nofollow noreferrer">bug 417655</a> which proposes <a href="https://git.eclipse.org/r/#/c/16619/" rel="nofollow noreferrer">the fix</a> in <a href="https://git.eclipse.org/r/#/c/16619/1/org.eclipse.egit.ui/src/org/eclipse/egit/ui/internal/history/GitHistoryPage.java" rel="nofollow noreferrer"><code>org.eclipse.egit.ui.internal.history.GitHistoryPage</code></a>.<br> Target Egit 3.1</p> </blockquote> <hr> <p>Original answer:</p> <p>This Egit exercice discusses the History View:</p> <p><img src="https://i.stack.imgur.com/W43z1.png" alt="https://raw.github.com/stefanlay/gittraining/master/exercises/egit/git/history-view-6.png"></p> <p>Consider the different button available in this view:</p> <p><img src="https://i.stack.imgur.com/fYQUR.png" alt="https://raw.github.com/stefanlay/gittraining/master/exercises/egit/git/history-view-buttons.png">:</p> <p>That tutorial mentions:</p> <blockquote> <p>TIP: If you got lost with the different filters and the history doesn’t show what you expect, set it back to show everything.<br> Therefore make sure that '<code>Show all branches and tags</code>' (<code>a</code>) is turned on and '<code>Show all changes in repository</code>' (<code>e</code>) is selected.</p> </blockquote> <p>Those two buttons should potentially show you all <em>reachable</em> (that is at least tagged) commits.</p> <hr> <p>The "<a href="http://wiki.eclipse.org/EGit/User_Guide#Filter_settings" rel="nofollow noreferrer">Filtering settings</a>" section of the <a href="http://wiki.eclipse.org/EGit/User_Guide" rel="nofollow noreferrer">Egit User Guide</a> is clear:</p> <blockquote> <p>The next four toggle buttons in the view toolbar control how the displayed commits are filtered with respect to the current input.</p> </blockquote> <p><img src="https://i.stack.imgur.com/3F4km.png" alt="http://wiki.eclipse.org/images/0/01/Egit-0.9-history-view-config.png"></p> <blockquote> <p>The buttons are working as radio buttons, i.e. one of the four buttons must always be down.</p> <ul> <li>If the "<code>Repository</code>" button is down, the commit log is not filtered and shows all commits reachable from the currently checked out branch (or all commits, see below about the "All Branches" action)</li> <li>If the "<code>Project</code>" button is down, the commit log is filtered to show all commits which affected any of the resources in the project containing the current input</li> <li>If the "<code>Folder</code>" toggle is down, the commit log is filtered to show all commits which affected any of the resources in the parent folder of the current input</li> <li>If the "<code>Resource</code>" button is down, the commit log is filtered to show only commits which affected the current input; the view menu item <code>Show &gt; Follow Renames</code> allows to toggle whether renames of the selected resource should be followed by this filter</li> </ul> <p>Note that not all combinations of filter setting and current input are meaningful; for example, if the current input is a project, the "Project" option is in fact the same as the "Resource" option.</p> </blockquote> <p>But the "<a href="http://wiki.eclipse.org/EGit/User_Guide#All_Branches" rel="nofollow noreferrer">All branches</a>" sections add:</p> <blockquote> <p>This toggle activates the "All Branches" mode.<br> <strong>By default, only those commits are shown in the commit log that can be reached from the currently checked out commit, i.e. the Commit Graph ends with the currently checked out commit and newer commits are not shown.</strong><br> If this button is down, all commits will be shown in the commit log. </p> </blockquote> <p><img src="https://i.stack.imgur.com/thjxT.png" alt="http://wiki.eclipse.org/images/c/c7/Egit-0.9-history-view-allbranchesToggle.png"></p> <p>In your case, I am not sure commits are show when referenced by a tag alone.<br> Only branches make those commits visible.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to show tags in the history view of egit?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USVonC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to show tags in the history view of egit?
      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. VTAcceptedByOriginator
    1. COI have already selected both of them. Still, the tagged-but-not-reachable-from-a-branch commit isnt shown.
      singulars
      1. PO
      1. USOznerol256
    2. CO@Oznerol256 then I am afraid only branches make those commit visible. I have edited the answer to include other relevant sections of the Egit User Guide.
      singulars
      1. PO
      1. USVonC
    3. CO`git log` is certainly able to make commits visible based on a tag. So the conclusion is, **egit history isnt as good as `git log`**
      singulars
      1. PO
      1. USOznerol256
 

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