You are viewing an historical archive of past issues. Please
report new issues to the appropriate project issue tracker on
GitHub.
Comments
-
Greg Hurrell
Summary changed:
- From: Update to Git v1.7.11.2
- To: Update to Git v1.7.11.3
-
Greg Hurrell
Notes from 1.7.11.3 release announcement:
The latest maintenance release Git v1.7.11.3 is now available at the usual places. The release tarballs are found at: http://code.google.com/p/git-core/downloads/list and their SHA-1 checksums are: a10c420e4d9152d6059f41825904cfac3062b135 git-1.7.11.3.tar.gz 41500708e87787d6139de413c4da91629aa79fa8 git-htmldocs-1.7.11.3.tar.gz 10151406ace1da92a70d203a7eb1c86024fdd919 git-manpages-1.7.11.3.tar.gz Also the following public repositories all have a copy of the v1.7.11.3 tag and the maint branch that the tag points at: url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git v1.7.11.3 Release Notes =========================== Fixes since v1.7.11.3 --------------------- * The error message from "git push $there :bogo" (and its equivalent "git push $there --delete bogo") mentioned that we tried and failed to guess what ref is being deleted based on the LHS of the refspec, which we don't. * A handful of files and directories we create had tighter than necessary permission bits when the user wanted to have group writability (e.g. by setting "umask 002"). * "commit --amend" used to refuse amending a commit with an empty log message, with or without "--allow-empty-message". * "git commit --amend --only --" was meant to allow "Clever" people to rewrite the commit message without making any change even when they have already changes for the next commit added to their index, but it never worked as advertised since it was introduced in 1.3.0 era. * Even though the index can record pathnames longer than 1<<12 bytes, in some places we were not comparing them in full, potentially replacing index entries instead of adding. * "git show"'s auto-walking behaviour was an unreliable and unpredictable hack; it now behaves just like "git log" does when it walks. * "git diff", "git status" and anything that internally uses the comparison machinery was utterly broken when the difference involved a file with "-" as its name. This was due to the way "git diff --no-index" was incorrectly bolted on to the system, making any comparison that involves a file "-" at the root level incorrectly read from the standard input. * We did not have test to make sure "git rebase" without extra options filters out an empty commit in the original history. * "git fast-export" produced an input stream for fast-import without properly quoting pathnames when they contain SPs in them. * "git checkout --detach", when you are still on an unborn branch, should be forbidden, but it wasn't. * Some implementations of Perl terminates "lines" with CRLF even when the script is operating on just a sequence of bytes. Make sure to use "$PERL_PATH", the version of Perl the user told Git to use, in our tests to avoid unnecessary breakages in tests. Also contains minor typofixes and documentation updates. ---------------------------------------------------------------- Changes since v1.7.11.2 are as follows: Alex Riesen (1): Restore umasks influence on the permissions of work tree created by clone Chris Webb (2): git-checkout: disallow --detach on unborn branch Allow edit of empty message with commit --amend Jay Soffian (1): fast-export: quote paths with spaces Jeff King (3): push: don't guess at qualifying remote refs on deletion add: create ADD_EDIT.patch with mode 0666 commit: fix "--amend --only" with no pathspec Junio C Hamano (10): show: fix "range implies walking" t/test-lib.sh: export PERL_PATH for use in scripts tests: enclose $PERL_PATH in double quotes t/README: add a bit more Don'ts diff-index.c: do not pretend paths are pathspecs diff-index.c: unify handling of command line paths diff-index.c: "git diff" has no need to read blob from the standard input rerere: make rr-cache fanout directory honor umask cache_name_compare(): do not truncate while comparing paths Git 1.7.11.3 Martin von Zweigbergk (1): add test case for rebase of empty commit Thomas Rast (1): Demonstrate git-show is broken with ranges Vincent van Ravesteijn (1): t: Replace 'perl' by $PERL_PATH -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
-
Greg Hurrell
Summary changed:
- From: Update to Git v1.7.11.3
- To: Update to Git v1.7.11.5
-
Greg Hurrell
Notes from the 1.7.11.5 release announcement:
The latest maintenance release Git v1.7.11.5 is now available at the usual places. The release tarballs are found at: http://code.google.com/p/git-core/downloads/list and their SHA-1 checksums are: 44013d9418ef23dd8bb67e80b27c9327356bfae8 git-1.7.11.5.tar.gz 8e19f56b2f484dc3327f1e8316c114dbe0ee2743 git-htmldocs-1.7.11.5.tar.gz d328241c130bbe38b12adf5702568c1edfff8623 git-manpages-1.7.11.5.tar.gz Also the following public repositories all have a copy of the v1.7.11.5 tag and the maint branch that the tag points at: url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git v1.7.11.5 Release Notes =========================== Fixes since v1.7.11.4 --------------------- * The Makefile rule to create assembly output (primarily for debugging purposes) did not create it next to the source. * The code to avoid mistaken attempt to add the object directory itself as its own alternate could read beyond end of a string while comparison. * On some architectures, "block-sha1" did not compile correctly when compilers inferred alignment guarantees from our source we did not intend to make. * When talking to a remote running ssh on IPv6 enabled host, whose address is spelled as "[HOST]:PORT", we did not parse the address correctly and failed to connect. * git-blame.el (in compat/) have been updated to use Elisp more correctly. * "git checkout <branchname>" to come back from a detached HEAD state incorrectly computed reachability of the detached HEAD, resulting in unnecessary warnings. * "git mergetool" did not support --tool-help option to give the list of supported backends, like "git difftool" does. * "git grep" stopped spawning an external "grep" long time ago, but a duplicated test to check internal and external "grep" was left behind. Also contains minor typofixes and documentation updates. ---------------------------------------------------------------- Changes since v1.7.11.4 are as follows: Heiko Voigt (1): link_alt_odb_entry: fix read over array bounds reported by valgrind Jeff King (1): checkout: don't confuse ref and object flags Jonathan Nieder (4): block-sha1: avoid pointer conversion that violates alignment constraints block-sha1: put expanded macro parameters in parentheses Makefile: fix location of listing produced by "make subdir/foo.s" Makefile: BLK_SHA1 does not require fast htonl() and unaligned loads Junio C Hamano (4): mergetool: support --tool-help option like difftool does Enumerate revision range specifiers in the documentation Prepare for 1.7.11.5 Git 1.7.11.5 Lawrence Mitchell (2): git-blame.el: Use with-current-buffer where appropriate git-blame.el: Do not use bare 0 to mean (point-min) Max Horn (1): Make <refname> documentation more consistent. Michael Schubert (1): Documentation/git-daemon: add missing word Ramkumar Ramachandra (1): commit: document a couple of options Ramsay Allan Jones (1): t7810-*.sh: Remove redundant test René Scharfe (1): git: Wrong parsing of ssh urls with IPv6 literals ignores port Rüdiger Sonderfeld (2): git-blame.el: use mapc instead of mapcar git-blame.el: Do not use goto-line in lisp code Štěpán Němec (1): doc: A few minor copy edits.
-
Greg Hurrell
Summary changed:
- From: Update to Git v1.7.11.5
- To: Update to Git v1.7.12
-
Greg Hurrell
Notes from the 1.7.12 release announcement:
The latest feature release Git v1.7.12 is now available at the usual places. The release tarballs are found at: http://code.google.com/p/git-core/downloads/list and their SHA-1 checksums are: 42ec1037f1ee5bfeb405710c83b73c0515ad26e6 git-1.7.12.tar.gz 50bbfeba77af9a411cc1a1e41220782cf3fd9b5e git-htmldocs-1.7.12.tar.gz fb572729ca5c60161dc651564a50d4378507e20f git-manpages-1.7.12.tar.gz Also the following public repositories all have a copy of the v1.7.12 tag and the master branch that the tag points at: url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git v1.7.12 Release Notes ========================= Updates since v1.7.11 --------------------- UI, Workflows & Features * Git can be told to normalize pathnames it read from readdir(3) and all arguments it got from the command line into precomposed UTF-8 (assuming that they come as decomposed UTF-8), in order to work around issues on Mac OS. I think there still are other places that need conversion (e.g. paths that are read from stdin for some commands), but this should be a good first step in the right direction. * Per-user $HOME/.gitconfig file can optionally be stored in $HOME/.config/git/config instead, which is in line with XDG. * The value of core.attributesfile and core.excludesfile default to $HOME/.config/git/attributes and $HOME/.config/git/ignore respectively when these files exist. * Logic to disambiguate abbreviated object names have been taught to take advantage of object types that are expected in the context, e.g. XXXXXX in the "git describe" output v1.2.3-gXXXXXX must be a commit object, not a blob nor a tree. This will help us prolong the lifetime of abbreviated object names. * "git apply" learned to wiggle the base version and perform three-way merge when a patch does not exactly apply to the version you have. * Scripted Porcelain writers now have access to the credential API via the "git credential" plumbing command. * "git help" used to always default to "man" format even on platforms where "man" viewer is not widely available. * "git clone --local $path" started its life as an experiment to optionally use link/copy when cloning a repository on the disk, but we didn't deprecate it after we made the option a no-op to always use the optimization. The command learned "--no-local" option to turn this off, as a more explicit alternative over use of file:// URL. * "git fetch" and friends used to say "remote side hung up unexpectedly" when they failed to get response they expect from the other side, but one common reason why they don't get expected response is that the remote repository does not exist or cannot be read. The error message in this case was updated to give better hints to the user. * "git help -w $cmd" can show HTML version of documentation for "git-$cmd" by setting help.htmlpath to somewhere other than the default location where the build procedure installs them locally; the variable can even point at a http:// URL. * "git rebase [-i] --root $tip" can now be used to rewrite all the history leading to "$tip" down to the root commit. * "git rebase -i" learned "-x <cmd>" to insert "exec <cmd>" after each commit in the resulting history. * "git status" gives finer classification to various states of paths in conflicted state and offer advice messages in its output. * "git submodule" learned to deal with nested submodule structure where a module is contained within a module whose origin is specified as a relative URL to its superproject's origin. * A rather heavy-ish "git completion" script has been split to create a separate "git prompting" script, to help lazy-autoloading of the completion part while making prompting part always available. * "gitweb" pays attention to various forms of credits that are similar to "Signed-off-by:" lines in the commit objects and highlights them accordingly. Foreign Interface * "mediawiki" remote helper (in contrib/) learned to handle file attachments. * "git p4" now uses "Jobs:" and "p4 move" when appropriate. * vcs-svn has been updated to clean-up compilation, lift 32-bit limitations, etc. Performance, Internal Implementation, etc. (please report possible regressions) * Some tests showed false failures caused by a bug in ecryptofs. * We no longer use AsciiDoc7 syntax in our documentation and favor a more modern style. * "git am --rebasing" codepath was taught to grab authorship, log message and the patch text directly out of existing commits. This will help rebasing commits that have confusing "diff" output in their log messages. * "git index-pack" and "git pack-objects" use streaming API to read from the object store to avoid having to hold a large blob object in-core while they are doing their thing. * Code to match paths with exclude patterns learned to avoid calling fnmatch() by comparing fixed leading substring literally when possible. * "git log -n 1 -- rarely-touched-path" was spending unnecessary cycles after showing the first change to find the next one, only to discard it. * "git svn" got a large-looking code reorganization at the last minute before the code freeze. Also contains minor documentation updates and code clean-ups. Fixes since v1.7.11 ------------------- Unless otherwise noted, all the fixes since v1.7.11 in the maintenance releases are contained in this release (see release notes to them for details). * "git submodule add" was confused when the superproject did not have its repository in its usual place in the working tree and GIT_DIR and GIT_WORK_TREE was used to access it. * "git commit --amend" let the user edit the log message and then died when the human-readable committer name was given insufficiently by getpwent(3).
-
Greg Hurrell
This is done on my development machines (see "Updating to Git 1.7.12").
Haven't done anything yet remotely.
-
Greg Hurrell
Status changed:
- From: new
- To: open
-
Greg Hurrell
Summary changed:
- From: Update to Git v1.7.12
- To: Update to Git v1.7.12.1
-
Greg Hurrell
v1.7.12.1 is out:
The latest maintenance release Git v1.7.12.1 is now available at the usual places. The release tarballs are found at: http://code.google.com/p/git-core/downloads/list and their SHA-1 checksums are: c5227b5202947bba3d63dca72662fad02d208800 git-1.7.12.1.tar.gz b42d5db34612825676d0a231cf9c566f8ad45e9f git-htmldocs-1.7.12.1.tar.gz 2d9c267c5370cdceb2e67f67abf5b152b0c18db9 git-manpages-1.7.12.1.tar.gz Also the following public repositories all have a copy of the v1.7.12.1 tag and the maint branch that the tag points at: url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git 1.7.12.1 Release Notes ========================== Fixes since v1.7.12 ------------------- * "git apply -p0" did not parse pathnames on "diff --git" line correctly. This caused patches that had pathnames in no other places to be mistakenly rejected (most notably, binary patch that does not rename nor change mode). Textual patches, renames or mode changes have preimage and postimage pathnames in different places in a form that can be parsed unambiguously and did not suffer from this problem. * "git cherry-pick A C B" used to replay changes in A and then B and then C if these three commits had committer timestamps in that order, which is not what the user who said "A C B" naturally expects. * "git commit --amend" let the user edit the log message and then died when the human-readable committer name was given insufficiently by getpwent(3). * Some capabilities were asked by fetch-pack even when upload-pack did not advertise that they are available. fetch-pack has been fixed not to do so. * "git diff" had a confusion between taking data from a path in the working tree and taking data from an object that happens to have name 0{40} recorded in a tree. * "git for-each-ref" did not correctly support more than one --sort option. * "git log .." errored out saying it is both rev range and a path when there is no disambiguating "--" is on the command line. Update the command line parser to interpret ".." as a path in such a case. * The "--topo-order", "--date-order" (and the lack of either means the default order) options to "rev-list" and "log" family of commands were poorly described in the documentation. * "git prune" without "-v" used to warn about leftover temporary files (which is an indication of an earlier aborted operation). * Pushing to smart HTTP server with recent Git fails without having the username in the URL to force authentication, if the server is configured to allow GET anonymously, while requiring authentication for POST. * The reflog entries left by "git rebase" and "git rebase -i" were inconsistent (the interactive one gave an abbreviated object name). * When "git push" triggered the automatic gc on the receiving end, a message from "git prune" that said it was removing cruft leaked to the standard output, breaking the communication protocol. * "git show --quiet" ought to be a synonym for "git show -s", but wasn't. * "git show --format='%ci'" did not give timestamp correctly for commits created without human readable name on "committer" line. * "git send-email" did not unquote encoded words that appear on the header correctly, and lost "_" from strings. * The interactive prompt "git send-email" gives was error prone. It asked "What e-mail address do you want to use?" with the address it guessed (correctly) the user would want to use in its prompt, tempting the user to say "y". But the response was taken as "No, please use 'y' as the e-mail address instead", which is most certainly not what the user meant. * "gitweb" when used with PATH_INFO failed to notice directories with SP (and other characters that need URL-style quoting) in them. * When the user gives an argument that can be taken as both a revision name and a pathname without disambiguating with "--", we used to give a help message "Use '--' to separate". The message has been clarified to show where that '--' goes on the command line. * When the user exports a non-default IFS without HT, scripts that rely on being able to parse "ls-files -s | while read a b c..." started to fail. Protect them from such a misconfiguration. * The attribute system may be asked for a path that itself or its leading directories no longer exists in the working tree, and it is fine if we cannot open .gitattribute file in such a case. Failure to open per-directory .gitattributes with error status other than ENOENT and ENOTDIR should be diagnosed, but it wasn't. * After "gitk" showed the contents of a tag, neither "Reread references" nor "Reload" did not update what is shown as the contents of it, when the user overwrote the tag with "git tag -f". * "ciabot" script (in contrib/) has been updated with extensive documentation. * "git-jump" script (in contrib/) did not work well when diff.noprefix or diff.mnemonicprefix is in effect. * Older parts of the documentation described as if having a regular file in .git/refs/ hierarchy were the only way to have branches and tags, which is not true for quite some time. * A utility shell function test_seq has been added as a replacement for the 'seq' utility found on some platforms. * Compatibility wrapper to learn the maximum number of file descriptors we can open around sysconf(_SC_OPEN_MAX) and getrlimit(RLIMIT_NO_FILE) has been introduced for portability. * We used curl_easy_strerror() without checking version of cURL, breaking the build for versions before curl 7.12.0. * Code to work around MacOS X UTF-8 gotcha has been cleaned up. * Fallback 'getpass' implementation made unportable use of stdio API. * The "--rebase" option to "git pull" can be abbreviated to "-r", but we didn't document it. * It was generally understood that "--long-option"s to many of our subcommands can be abbreviated to the unique prefix, but it was not easy to find it described for new readers of the documentation set. * The synopsis said "checkout [-B branch]" to make it clear the branch name is a parameter to the option, but the heading for the option description was "-B::", not "-B branch::", making the documentation misleading. Also contains numerous documentation updates. ---------------------------------------------------------------- Changes since v1.7.12 are as follows: Adam Butcher (1): Fix '\ No newline...' annotation in rewrite diffs Adam Spiers (1): Add missing -z to git check-attr usage text for consistency with man page Andreas Schwab (1): Documentation/git-filter-branch: Move note about effect of removing commits Brandon Casey (2): t/t5400: demonstrate breakage caused by informational message from prune prune.c: only print informational message in show_only or verbose mode David Aguilar (2): gitk: Teach "Reread references" to reload tags gitk: Rename 'tagcontents' to 'cached_tagcontent' Eric S. Raymond (4): fast-import: document the --done option contrib/ciabot: Get ciabot configuration from git variables Improved documentation for the ciabot scripts. Make the ciabot scripts completely self-configuring in the normal case. Felipe Contreras (1): gitk: Avoid Meta1-F5 Heiko Voigt (2): Let submodule command exit with error status if path does not exist Documentation/CodingGuidelines: spell out more shell guidelines Jay Soffian (1): gitweb: URL-decode $my_url/$my_uri when stripping PATH_INFO Jeff King (29): diff: do not use null sha1 as a sentinel value do not write null sha1s to on-disk index fsck: detect null sha1 in tree entries include agent identifier in capability string docs: monospace listings in docbook output check-docs: mention gitweb specially check-docs: update non-command documentation list command-list: add git-sh-i18n command-list: mention git-credential-* helpers check-docs: factor out command-list check-docs: list git-gui as a command check-docs: drop git-help special-case check-docs: get documented command list from Makefile send-pack: fix capability-sending logic do not send client agent unless server does first parse_feature_request: make it easier to see feature values fetch-pack: mention server version with verbose output config: warn on inaccessible files gitignore: report access errors of exclude files attr: warn on inaccessible attribute files t5550: put auth-required repo in auth/dumb t5550: factor out http auth setup t/lib-httpd: only route auth/dumb to dumb repos t/lib-httpd: recognize */smart/* repos as smart-http t: test basic smart-http authentication t: test http access to "half-auth" repositories http: factor out http error code handling http: prompt for credentials on failed POST log: fix --quiet synonym for -s Joachim Schmitz (2): http.c: don't use curl_easy_strerror prior to curl-7.12.0 sha1_file.c: introduce get_max_fd_limit() helper Junio C Hamano (34): test: rename $satisfied to $satisfied_prereq test: allow prerequisite to be evaluated lazily config: "git config baa" should exit with status 1 t7406: fix misleading "rev-parse --max-count=1 HEAD" sane_execvp(): ignore non-directory on $PATH Documentation: do not mention .git/refs/* directories receive-pack: do not leak output from auto-gc to standard output sh-setup: protect from exported IFS fetch-pack: do not ask for unadvertised capabilities send-email: validate & reconfirm interactive responses rev-list docs: clarify --topo-order description gitcli: describe abbreviation of long options Documentation: update the introductory section git-config doc: unconfuse an example precompose-utf8: do not call checks for non-ascii "utf8" warn_on_inaccessible(): a helper to warn on inaccessible paths specifying ranges: we did not mean to make ".." an empty set mergetool: style fixes Prepare for 1.7.11.6 apply: compute patch->def_name correctly under -p0 doc: "git checkout -b/-B/--orphan" always takes a branch name split_ident_line(): make best effort when parsing author/committer line Document file-glob for "git checkout -- '*.c'" gitcli: formatting fix gitcli: contrast wildcard given to shell and to git Almost 1.7.11.6 Start preparing for 1.7.12.1 Git 1.7.11.6 Further merging down for 1.7.12.1 Further merging in preparation for 1.7.12.1 attr: failure to open a .gitattributes file is OK with ENOTDIR Git 1.7.11.7 Draft release notes to 1.7.12.1 Git 1.7.12.1 Kacper Kornet (2): t6300: test sort with multiple keys for-each-ref: Fix sort with multiple keys Martin von Zweigbergk (4): add tests for 'git rebase --keep-empty' teach log --no-walk=unsorted, which avoids sorting demonstrate broken 'git cherry-pick three one two' cherry-pick/revert: respect order of revisions to pick Matthieu Moy (1): setup: clarify error messages for file/revisions ambiguity Michael Haggerty (1): git-config.txt: fix example Michael J Gruber (6): test-lib: provide case insensitivity as a prerequisite t0050: use the CASE_INSENSITIVE_FS test prereq t0050: use the SYMLINKS test prereq test-lib: provide UTF8 behaviour as a prerequisite rebase -i: use full onto sha1 in reflog t3910: use the UTF8_NFD_TO_NFC test prereq Michał Kiedrowicz (1): tests: Introduce test_seq Miklos Vajna (1): man: git pull -r is a short for --rebase Mischa POSLAWSKY (1): git-jump: ignore (custom) prefix in diff mode Nguyễn Thái Ngọc Duy (1): read_index_from: remove bogus errno assignments Paul Gortmaker (1): apply: delete unused deflate_origlen from patch struct Phil Hord (2): test: git-stash conflict sets up rerere stash: invoke rerere in case of conflict Philip Oakley (1): Doc: Improve shallow depth wording Ramkumar Ramachandra (1): t/perf: add "trash directory" to .gitignore Ramsay Allan Jones (1): test-regex: Add a test to check for a bug in the regex routines Robin Rosenberg (1): cleanup precompose_utf8 Stefan Zager (1): Make 'git submodule update --force' always check out submodules. Stephen Boyd (1): send-email: initial_to and initial_reply_to are both optional Thomas Rast (3): send-email: improve RFC2047 quote parsing diff_setup_done(): return void merge-recursive: eliminate flush_buffer() in favor of write_in_full() Wesley J. Landaker (1): Documentation: indent-with-non-tab uses "equivalent tabs" not 8 Yacine Belkadi (1): completion: add --no-edit to git-commit
-
Greg Hurrell
Summary changed:
- From: Update to Git v1.7.12.1
- To: Update to Git v1.7.12.2
-
Greg Hurrell
1.7.12.2 release announcement:
The latest maintenance release Git v1.7.12.2 is now available at the usual places. The release tarballs are found at: http://code.google.com/p/git-core/downloads/list and their SHA-1 checksums are: 277b759139ddb62c6935da37de8a483e2c234a97 git-1.7.12.2.tar.gz 5722156394c7478b2339a1d87aa894bc4d2f5d6b git-htmldocs-1.7.12.2.tar.gz 8cf6fd255e83226b4abcdcd68dcf315c1995fd92 git-manpages-1.7.12.2.tar.gz Also the following public repositories all have a copy of the v1.7.12.2 tag and the maint branch that the tag points at: url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git 1.7.12.2 Release Notes ========================== Fixes since v1.7.12.1 --------------------- * When "git am" is fed an input that has multiple "Content-type: ..." header, it did not grok charset= attribute correctly. * Even during a conflicted merge, "git blame $path" always meant to blame uncommitted changes to the "working tree" version; make it more useful by showing cleanly merged parts as coming from the other branch that is being merged. * "git blame MAKEFILE" run in a history that has "Makefile" but not "MAKEFILE" should say "No such file MAKEFILE in HEAD", but got confused on a case insensitive filesystem and failed to do so. * "git fetch --all", when passed "--no-tags", did not honor the "--no-tags" option while fetching from individual remotes (the same issue existed with "--tags", but combination "--all --tags" makes much less sense than "--all --no-tags"). * "git log/diff/format-patch --stat" showed the "N line(s) added" comment in user's locale and caused careless submitters to send patches with such a line in them to projects whose project language is not their language, mildly irritating others. Localization to the line has been disabled for now. * "git log --all-match --grep=A --grep=B" ought to show commits that mention both A and B, but when these three options are used with --author or --committer, it showed commits that mention either A or B (or both) instead. * The subcommand to remove the definition of a remote in "git remote" was named "rm" even though all other subcommands were spelled out. Introduce "git remote remove" to remove confusion, and keep "rm" as a backward compatible synonym. Also contains a handful of documentation updates. ---------------------------------------------------------------- Changes since v1.7.12.1 are as follows: Dan Johnson (1): fetch --all: pass --tags/--no-tags through to each remote David Gould (1): run-command.c: fix broken list iteration in clear_child_for_cleanup Felipe Contreras (1): completion: fix shell expansion of items Jeff King (4): argv-array: add pop function argv-array: fix bogus cast when freeing array fetch: use argv_array instead of hand-building arrays Revert "completion: fix shell expansion of items" Jens Lehmann (1): submodule: use argv_array instead of hand-building arrays Jeremy White (1): Documentation: describe subject more precisely Jonathan "Duke" Leto (1): Improve the description of GIT_PS1_SHOWUPSTREAM Junio C Hamano (11): mailinfo: strip "RE: " prefix blame $path: avoid getting fooled by case insensitive filesystems blame: allow "blame file" in the middle of a conflicted merge grep: teach --debug option to dump the parse tree log --grep/--author: honor --all-match honored for multiple --grep patterns log: document use of multiple commit limiting options grep.c: mark private file-scope symbols as static mailinfo: do not concatenate charset= attribute values from mime headers grep.c: make two symbols really file-scope static this time Start preparation for 1.7.12.2 Git 1.7.12.2 Michael J Gruber (6): grep: show --debug output only once t7810-grep: bring log --grep tests in common form t7810-grep: test multiple --grep with and without --all-match t7810-grep: test multiple --author with --all-match t7810-grep: test interaction of multiple --grep and --author options t7810-grep: test --all-match with multiple --grep and --author options Nguyễn Thái Ngọc Duy (3): remote: prefer subcommand name 'remove' to 'rm' doc: move rev-list option -<n> from git-log.txt to rev-list-options.txt Revert diffstat back to English Ralf Thielow (1): l10n: de.po: correct translation of a 'rebase' message Stefan Naewe (1): ls-remote: document the '--get-url' option Stephen Boyd (1): Documentation: Document signature showing options Thynson (2): l10n: Unify the translation for '(un)expected' l10n: Improve many translation for zh_CN
-
Greg Hurrell
Summary changed:
- From: Update to Git v1.7.12.2
- To: Update to Git v1.7.12.3
-
Greg Hurrell
The latest maintenance release Git v1.7.12.3 is now available at the usual places. The release tarballs are found at: http://code.google.com/p/git-core/downloads/list and their SHA-1 checksums are: a071f03f6aab76b283828db1fdedbedb90085eb5 git-1.7.12.3.tar.gz 6f976c27aab7250f1a35b2b002ac7a07c3266cf4 git-htmldocs-1.7.12.3.tar.gz 49584f0b72e4a13f9a4df771bbde9cf70f25d317 git-manpages-1.7.12.3.tar.gz Also the following public repositories all have a copy of the v1.7.12.3 tag and the maint branch that the tag points at: url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git Git 1.7.12.3 Release Notes ========================== Fixes since v1.7.12.2 --------------------- * "git am" mishandled a patch attached as application/octet-stream (e.g. not text/*); Content-Transfer-Encoding (e.g. base64) was not honored correctly. * It was unclear in the documentation for "git blame" that it is unnecessary for users to use the "--follow" option. * A repository created with "git clone --single" had its fetch refspecs set up just like a clone without "--single", leading the subsequent "git fetch" to slurp all the other branches, defeating the whole point of specifying "only this branch". * "git fetch" over http had an old workaround for an unlikely server misconfiguration; it turns out that this hurts debuggability of the configuration in general, and has been reverted. * "git fetch" over http advertised that it supports "deflate", which is much less common, and did not advertise the more common "gzip" on its Accept-Encoding header. * "git receive-pack" (the counterpart to "git push") did not give progress output while processing objects it received to the puser when run over the smart-http protocol. * "git status" honored the ignore=dirty settings in .gitmodules but "git commit" didn't. Also contains a handful of documentation updates. ---------------------------------------------------------------- Changes since v1.7.12.2 are as follows: Jeff King (3): receive-pack: redirect unpack-objects stdout to /dev/null receive-pack: send pack-processing stderr over sideband receive-pack: drop "n/a" on unpacker errors Junio C Hamano (3): git blame: document that it always follows origin across whole-file renames Start preparing for 1.7.12.3 Git 1.7.12.3 Linus Torvalds (1): mailinfo: don't require "text" mime type for attachments Orgad Shaneh (1): commit: pay attention to submodule.$name.ignore in .gitmodules Peter Krefting (1): l10n: Fix to Swedish translation Ralf Thielow (1): clone --single: limit the fetch refspec to fetched branch Ramkumar Ramachandra (1): submodule: if $command was not matched, don't parse other args Shawn O. Pearce (2): Revert "retry request without query when info/refs?query fails" Enable info/refs gzip decompression in HTTP client
-
Greg Hurrell
This ticket is getting out of control. Closing in favor of issue #2016 (which is about upgrading to Git 1.7.12.4.
-
Greg Hurrell
Status changed:
- From: open
- To: closed
Add a comment
Comments are now closed for this issue.