Sunday, February 24, 2013

More leftover bits

I've spent the past few days to see if there were discussions that are worth salvaging but somehow petered out without reaching conclusion, veered into tangent, or did not even start.

I tried to be fairly thorough, but I am sure I have missed some. Note that I deliberately excluded ones that fall into the Nobody who knows what they are talking about has any idea how to approach this feature category. I also left out discussions that are fairly young, hoping that they will stay alive without me keeping track of them.

Teach "--first-parent" to "git rebase" to deal better with a history with (possibly evil) merges from side branches.Cf. $gmane/198516

More fixes to bring sanity to "git diff --no-index", some discussed in the thread are definitely worthwhile, while some others are not.
Cf. $gmane/200769

The name sanitization code may be overly conservative.
Cf. $gmane/200823

The behaviour of "git filter-branch" around annotated tag may be under-documented to cause misunderstanding on the user's part, or it could be simply buggy.
Cf. $gmane/212353

Annotating a pair of commit objects and trigger interesting behaviour when they both appear in the history.
Cf. $gmane/212570

Make it safer to export mandir, htmldir, etc. from the top-level to Documentation/ Makefile.
Cf. $gmane/216222

Come up with a better default selection logic than the tentative "use the remote-tracking branch of the destination" for --force-with-lease optionCf. $gmane/230483

Force "git format-patch" (or at least allow it to be configured back to normal, when the user wants to use nonstandard settings for other commands) to use standard --commit-abbrev and --no-numstat settings.

Discuss and decide if we want to choose between the "mode word" UI (e.g. "git submodule add") and the "mode option" UI (e.g. "git tag --delete") and standardise on one; if it turns out to be a good idea, devise the migration plan to break the backward-compatibility.Cf. $gmane/231478