Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: git/git
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: bcd45b4085f9269a536c8fb1963ac8380bfac0e8
Choose a base ref
...
head repository: git/git
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: eff80a9fd990de3605063050dae32f969ef18ba8
Choose a head ref
  • 1 commit
  • 20 files changed
  • 1 contributor

Commits on Jan 16, 2013

  1. Allow custom "comment char" 

    Some users do want to write a line that begin with a pound sign, #,
in their commit log message.  Many tracking system recognise
a token of #<bugid> form, for example.

The support we offer these use cases is not very friendly to the end
users.  They have a choice between

 - Don't do it.  Avoid such a line by rewrapping or indenting; and

 - Use --cleanup=whitespace but remove all the hint lines we add.

Give them a way to set a custom comment char, e.g.

    $ git -c core.commentchar="%" commit

so that they do not have to do either of the two workarounds.

[jc: although I started the topic, all the tests and documentation
updates, many of the call sites of the new strbuf_add_commented_*()
functions, and the change to git-submodule.sh scripted Porcelain are
from Ralf.]

Signed-off-by: Junio C Hamano <[email protected]>
Signed-off-by: Ralf Thielow <[email protected]>
Signed-off-by: Junio C Hamano <[email protected]>
    @gitster
    gitster committed Jan 16, 2013
    Configuration menu
    Copy the full SHA
    eff80a9 View commit details
    Browse the repository at this point in the history
Loading