Re: [PATCH 2/2] sort_in_topological_order(): avoid setting a commit flag
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jul 23, 2008, 01:01 UTC
- Message-ID
- <7v7ibdifbp.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <alpine.DEB.1.00.0807230150480.8986@racer>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 7 quoted lines
> This is the same behavior as before, since indegree could not be > non-zero when TOPOSORT was unset. > > Incidentally, this fixes the bug in show-branch where the 8th column > was not shown: show-branch sorts the commits in topological order, > assuming that all the commit flags are available for show-branch's > private matters.
Do people still actively use show-branch as a G/CUI, especially after that "log --graph" thing was introduced?
If that is the case, it might also make sense to stop using the object flags but allocate necessary number of bits (not restricted to 25 or so) pointed at by commit->util field to remove its limitation.
Hint, hint...