Overlong lines with git-merge --log
Hey all. Using git-merge --log to merge commit messages that spawn multiple lines will produce overlong summary lines. That's because each summary line for a commit includes the entire commit message (all lines concatenated). According to git-fmt-merge-msg(1), --log should 'populate the log message with one-line descriptions' instead of using the entire commit messages. Which would make a lot of sense, it's just not working as advertised. Encountered with git version 1.7.9.5. -- Yours sincerely, Tim Janik --- http://timj.testbit.eu/ - Free software Author -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Overlong lines with git-merge --log
On 02.11.2012 11:05, Jeff King wrote: Taking just the first line of those often cuts off the useful part. It was deemed less bad to show the whole message as a subject rather than cut it off arbitrarily. Thanks a lot for the explanation, I'm using git directly here, but the two cases I had indeed lacked this newline. -- Yours sincerely, Tim Janik --- http://timj.testbit.eu/ - Free software Author -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
fetch unshallow fails to honor dry-run
Hey all, git fetch --dry-run modifies the repository if --unshallow is passed: $ git --version git version 2.1.4 $ git fetch --dry-run --unshallow remote: Counting objects: 30603, done. remote: Compressing objects: 100% (6843/6843), done. remote: Total 30603 (delta 24564), reused 29164 (delta 23386) Receiving objects: 100% (30603/30603), 5.42 MiB | 0 bytes/s, done. Resolving deltas: 100% (24564/24564), completed with 317 local objects. remote: Counting objects: 7, done. remote: Compressing objects: 100% (7/7), done. remote: Total 7 (delta 0), reused 6 (delta 0) Unpacking objects: 100% (7/7), done. I actually tried --dry-run --unshallow in order to find a way to detect in a script if the current git repository is shallow or not. Better suggestions to find this out are very welcome. -- Yours sincerely, Tim Janik https://testbit.eu/timj/ Free software author and speaker. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
