This will need to be carefully examined since the current commands issued already cope with a number of edge cases. The other option might be to find a set of git log options which doesn't use -topo-order all the time but also doesn't report the commits out of order in this case. Edit: These are the suggestions given in the other answers. All these things have a performance impact which will need to be assessed, given that this doesn't happen very often and that the user can easily work around it with the Ancestor Order option already. gitg - GTK+/GNOME clone of GitX tig - text mode interface for git, is GUI and pager, uses ncurses. Therefore we'd need to keep a running record of all the SHAs encountered so far. You can't actually tell that it's happened until you see a case where a parent commit has already been encountered by the time the child commit referring to it appears. It would be nice to be able to detect this case and auto-enable the Ancestor Order option, although this will require the log to be completely refreshed. For example, you can run gitx -all to display all branches in the repository, or gitx - Documentation to only show commits relating to the Documentation subdirectory. Gitk is easiest to invoke from the command-line. This is the tool to use when you’re trying to find something that happened in the past, or visualize your project’s history. The most important reason people chose GitX-dev is. This option is slower than the date order though, which is why it is not the default. Think of it like a powerful GUI shell over git log and git grep. In the questionWhat are the best Git clients for macOS GitX-dev is ranked 8th while gitk is ranked 14th. To use some other application for viewing Git history, such as GitX or QGit. Because the SourceTree log relies on a child commit being reported before its parent, this can cause incorrect graph rendering.Ī workaround for this is simply to select 'Ancestor Order' in the log options. Select Edit > Preferences > Version Control > Git, and then select the Set. Ive checked the rendering of Gitk, GitX, and Tower, and they all re-sort and render these out of time commits just fine without sacrificing interweaving. If multiple commits are created with the same timestamp, either via 'git-svn dcommit' when there is more than one commit outstanding, or when using 'git rebase -i' to rewrite multiple changesets, if one of those commits is given a tag (or possibly a branch), git log is prone to reporting them out of order.
0 Comments
Leave a Reply. |