- "git send-email" can be told not to thread the messages when
sending out more than one patches.
+ - "git send-email" can also be told how to find whom to cc the
+ message to for each message via --cc-cmd.
+
- "git config" learned NUL terminated output format via -z to
help scripts.
- "git clone" uses -l (hardlink files under .git) by default when
cloning locally.
+ - URL used for "git clone" and friends can specify nonstandard SSH port
+ by using sh://host:port/path/to/repo syntax.
+
- "git bundle create" can now create a bundle without negative refs,
i.e. "everything since the beginning up to certain points".
recursively descends into trees by default.
- "git diff" does not show differences that come only from
- stat-dirtiness in the form of "diff --git" header anymore. When
- generating a textual diff, it shows a warning message at the end.
+ stat-dirtiness in the form of "diff --git" header anymore.
+ It runs "update-index --refresh" silently as needed.
+
+ - "git tag -l" used to match tags by globbing its parameter as if it
+ has wildcard '*' on both ends, which made "git tag -l gui" to match
+ tag 'gitgui-0.7.0'; this was very annoying. You now have to add
+ asterisk on the sides you want to wildcard yourself.
- The editor to use with many interactive commands can be
overridden with GIT_EDITOR environment variable, or if it
- "gitweb" had trouble handling non UTF-8 text with older
Encode.pm Perl module.
+ - "git svn" misparsed the data from the commits in the repository when
+ the user had "color.diff = true" in the configuration. This has been
+ fixed.
+
+ - There was a case where "git svn dcommit" clobbered changes made on the
+ SVN side while committing multiple changes.
+
- "git-write-tree" had a bad interaction with racy-git avoidance and
gitattributes mechanisms.
inconsistency was introduced somewhere in v1.3.0 series but now has
been corrected.
---
-exec >/var/tmp/1
-O=v1.5.3-rc7-15-ga65f200
-echo O=`git describe refs/heads/master`
-git shortlog --no-merges $O..refs/heads/master ^refs/heads/maint
+ - "git rebase -m" incorrectly displayed commits that were skipped.
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
<div class="verseblock">\r
-<div class="content"><em>git-rebase</em> [-i | --interactive] [-v | --verbose] [--merge] [-C<n>]\r
+<div class="content"><em>git-rebase</em> [-i | --interactive] [-v | --verbose] [-m | --merge] [-C<n>]\r
[-p | --preserve-merges] [--onto <newbase>] <upstream> [<branch>]\r
<em>git-rebase</em> --continue | --skip | --abort</div></div>\r
</div>\r
</p>\r
</dd>\r
<dt>\r
---merge\r
+-m, --merge\r
</dt>\r
<dd>\r
<p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 01-Sep-2007 11:16:26 UTC\r
+Last updated 02-Sep-2007 06:24:43 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
[verse]
-'git-rebase' [-i | --interactive] [-v | --verbose] [--merge] [-C<n>]
+'git-rebase' [-i | --interactive] [-v | --verbose] [-m | --merge] [-C<n>]
[-p | --preserve-merges] [--onto <newbase>] <upstream> [<branch>]
'git-rebase' --continue | --skip | --abort
--skip::
Restart the rebasing process by skipping the current patch.
---merge::
+-m, \--merge::
Use merging strategies to rebase. When the recursive (default) merge
strategy is used, this allows rebase to be aware of renames on the
upstream side.
<p>The --cc option must be repeated for each user you want on the cc list.</p>\r
</dd>\r
<dt>\r
+--cc-cmd\r
+</dt>\r
+<dd>\r
+<p>\r
+ Specify a command to execute once per patch file which\r
+ should generate patch file specific "Cc:" entries.\r
+ Output of this command must be single email address per line.\r
+ Default is the value of <em>sendemail.cccmd</em> configuration value.\r
+</p>\r
+</dd>\r
+<dt>\r
--chain-reply-to, --no-chain-reply-to\r
</dt>\r
<dd>\r
</p>\r
</dd>\r
<dt>\r
+sendemail.cccmd\r
+</dt>\r
+<dd>\r
+<p>\r
+ Command to execute to generate per patch file specific "Cc:"s.\r
+</p>\r
+</dd>\r
+<dt>\r
sendemail.bcc\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 21-Aug-2007 02:20:20 UTC\r
+Last updated 02-Sep-2007 06:24:43 UTC\r
</div>\r
</div>\r
</body>\r
+
The --cc option must be repeated for each user you want on the cc list.
+--cc-cmd::
+ Specify a command to execute once per patch file which
+ should generate patch file specific "Cc:" entries.
+ Output of this command must be single email address per line.
+ Default is the value of 'sendemail.cccmd' configuration value.
+
--chain-reply-to, --no-chain-reply-to::
If this is set, each email will be sent as a reply to the previous
email sent. If disabled with "--no-chain-reply-to", all emails after
Format of the file(s) specified in sendemail.aliasesfile. Must be
one of 'mutt', 'mailrc', 'pine', or 'gnus'.
+sendemail.cccmd::
+ Command to execute to generate per patch file specific "Cc:"s.
+
sendemail.bcc::
Email address (or alias) to always bcc.