From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4986 invoked by alias); 25 Apr 2009 12:46:28 -0000 Received: (qmail 2834 invoked by uid 22791); 25 Apr 2009 12:38:17 -0000 X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_31,J_CHICKENPOX_32,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Message-ID: <49F30434.6040102@byu.net> Date: Sat, 25 Apr 2009 12:46:00 -0000 From: Eric Blake Reply-To: The Cygwin Mailing List User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: cygwin-announce@cygwin.com Subject: [1.7] Updated: git-1.6.2.4-1, git{k,-gui,-completion}-1.6.2.4-1 Content-Type: multipart/mixed; boundary="------------020703030901050602060901" Mailing-List: contact cygwin-announce-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-announce-owner@cygwin.com Reply-To: The Cygwin Mailing List Mail-Followup-To: cygwin-announce@cygwin.com X-SW-Source: 2009-04/txt/msg00042.txt.bz2 This is a multi-part message in MIME format. --------------020703030901050602060901 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-length: 3052 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A new release of git, 1.6.2.4-1, has been uploaded for those testing cygwin 1.7. For those using cygwin 1.5.x, 1.6.1.2-1 remains current. NEWS: ===== This is a new upstream major release. Additionally, the move to cygwin 1.7 allows the inclusion of IPv6 support, use of d_type, longer file names, and hopefully better multibyte character support. I'm attaching the release notes; see also the package documentation in /usr/share/doc/git/. When compiled out of the box, the upstream git maintainers cater to older cygwin releases, and intentionally disable certain features that have been reported on their mailing list, even though they work with the latest cygwin. Therefore, this build turns those features back on. However, it means that this version does assume that you are not using FAT or FAT32 to hold your repositories, since they do not store file permissions very accurately. DESCRIPTION: ============ Git is popular version control system designed to handle very large projects with speed and efficiency; it is used mainly for various open source projects, most notably the Linux kernel. Git falls in the category of distributed source code management tools, similar to e.g. GNU Arch or Monotone (or BitKeeper in the proprietary world). Every Git working directory is a full-fledged repository with full revision tracking capabilities, not dependent on network access or a central server. UPDATE: ======= To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions and pick up 'git', 'gitk', 'git-gui', and/or 'git-completion' from the 'Devel' category. DOWNLOAD: ========= Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: ========== If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. - -- Eric Blake volunteer cygwin git maintainer CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: ================================= To unsubscribe to the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-YOU=YOURDOMAIN.COM@cygwin.com If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknzBDQACgkQ84KuGfSFAYAJSACeMHRK8sirOrJDf5PGneoWpmP5 za4AniAjp/8rkkMXjpcH5AThZ4uL1T0j =0rEF -----END PGP SIGNATURE----- --------------020703030901050602060901 Content-Type: text/plain; name="NEWS.short" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="NEWS.short" Content-length: 11572 GIT v1.6.2.4 Release Notes ========================== Fixes since v1.6.2.3 -------------------- * The configuration parser had a buffer overflow while parsing an overlong value. * pruning reflog entries that are unreachable from the tip of the ref during "git reflog prune" (hence "git gc") was very inefficient. * "git-add -p" lacked a way to say "q"uit to refuse staging any hunks for the remaining paths. You had to say "d" and then ^C. * "git-checkout " did not update the index entry at the named path; it now does. * "git-fast-export" choked when seeing a tag that does not point at commit. * "git init" segfaulted when given an overlong template location via the --template= option. * "git-ls-tree" and "git-diff-tree" used a pathspec correctly when deciding to descend into a subdirectory but they did not match the individual paths correctly. This caused pathspecs "abc/d ab" to match "abc/0" ("abc/d" made them decide to descend into the directory "abc/", and then "ab" incorrectly matched "abc/0" when it shouldn't). * "git-merge-recursive" was broken when a submodule entry was involved in a criss-cross merge situation. Many small documentation updates are included as well. --- exec >/var/tmp/1 echo O=$(git describe maint) O=v1.6.2.3-38-g318b847 git shortlog --no-merges $O..maint GIT v1.6.2.3 Release Notes ========================== Fixes since v1.6.2.2 -------------------- * Setting an octal mode value to core.sharedrepository configuration to restrict access to the repository to group members did not work as advertised. * A fairly large and trivial memory leak while rev-list shows list of reachable objects has been identified and plugged. * "git-commit --interactive" did not abort when underlying "git-add -i" signaled a failure. * git-repack (invoked from git-gc) did not work as nicely as it should in a repository that borrows objects from neighbours via alternates mechanism especially when some packs are marked with the ".keep" flag to prevent them from being repacked. Many small documentation updates are included as well. GIT v1.6.2.2 Release Notes ========================== Fixes since v1.6.2.1 -------------------- * A longstanding confusing description of what --pickaxe option of git-diff does has been clarified in the documentation. * "git-blame -S" did not quite work near the commits that were given on the command line correctly. * "git diff --pickaxe-regexp" did not count overlapping matches correctly. * "git diff" did not feed files in work-tree representation to external diff and textconv. * "git-fetch" in a repository that was not cloned from anywhere said it cannot find 'origin', which was hard to understand for new people. * "git-format-patch --numbered-files --stdout" did not have to die of incompatible options; it now simply ignores --numbered-files as no files are produced anyway. * "git-ls-files --deleted" did not work well with GIT_DIR&GIT_WORK_TREE. * "git-read-tree A B C..." without -m option has been broken for a long time. * git-send-email ignored --in-reply-to when --no-thread was given. * 'git-submodule add' did not tolerate extra slashes and ./ in the path it accepted from the command line; it now is more lenient. * git-svn misbehaved when the project contained a path that began with two dashes. * import-zips script (in contrib) did not compute the common directory prefix correctly. * miscompilation of negated enum constants by old gcc (2.9) affected the codepaths to spawn subprocesses. Many small documentation updates are included as well. GIT v1.6.2.1 Release Notes ========================== Fixes since v1.6.2 ------------------ * .gitignore learned to handle backslash as a quoting mechanism for comment introduction character "#". * timestamp output in --date=relative mode used to display timestamps that are long time ago in the default mode; it now uses "N years M months ago", and "N years ago". * git-add -i/-p now works with non-ASCII pathnames. * "git hash-object -w" did not read from the configuration file from the correct .git directory. * git-send-email learned to correctly handle multiple Cc: addresses. GIT v1.6.2 Release Notes ======================== With the next major release, "git push" into a branch that is currently checked out will be refused by default. You can choose what should happen upon such a push by setting the configuration variable receive.denyCurrentBranch in the receiving repository. To ease the transition plan, the receiving repository of such a push running this release will issue a big warning when the configuration variable is missing. Please refer to: http://git.or.cz/gitwiki/GitFaq#non-bare http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007 for more details on the reason why this change is needed and the transition plan. For a similar reason, "git push $there :$killed" to delete the branch $killed in a remote repository $there, if $killed branch is the current branch pointed at by its HEAD, gets a large warning. You can choose what should happen upon such a push by setting the configuration variable receive.denyDeleteCurrent in the receiving repository. Updates since v1.6.1 -------------------- (subsystems) * git-svn updates. * gitweb updates, including a new patch view and RSS/Atom feed improvements. * (contrib/emacs) git.el now has commands for checking out a branch, creating a branch, cherry-picking and reverting commits; vc-git.el is not shipped with git anymore (it is part of official Emacs). (performance) * pack-objects autodetects the number of CPUs available and uses threaded version. (usability, bells and whistles) * automatic typo correction works on aliases as well * @{-1} is a way to refer to the last branch you were on. This is accepted not only where an object name is expected, but anywhere a branch name is expected and acts as if you typed the branch name. E.g. "git branch --track mybranch @{-1}", "git merge @{-1}", and "git rev-parse --symbolic-full-name @{-1}" would work as expected. * When refs/remotes/origin/HEAD points at a remote tracking branch that has been pruned away, many git operations issued warning when they internally enumerated the refs. We now warn only when you say "origin" to refer to that pruned branch. * The location of .mailmap file can be configured, and its file format was enhanced to allow mapping an incorrect e-mail field as well. * "git add -p" learned 'g'oto action to jump directly to a hunk. * "git add -p" learned to find a hunk with given text with '/'. * "git add -p" optionally can be told to work with just the command letter without Enter. * when "git am" stops upon a patch that does not apply, it shows the title of the offending patch. * "git am --directory=" and "git am --reject" passes these options to underlying "git apply". * "git am" learned --ignore-date option. * "git blame" aligns author names better when they are spelled in non US-ASCII encoding. * "git clone" now makes its best effort when cloning from an empty repository to set up configuration variables to refer to the remote repository. * "git checkout -" is a shorthand for "git checkout @{-1}". * "git cherry" defaults to whatever the current branch is tracking (if exists) when the argument is not given. * "git cvsserver" can be told not to add extra "via git-CVS emulator" to the commit log message it serves via gitcvs.commitmsgannotation configuration. * "git cvsserver" learned to handle 'noop' command some CVS clients seem to expect to work. * "git diff" learned a new option --inter-hunk-context to coalesce close hunks together and show context between them. * The definition of what constitutes a word for "git diff --color-words" can be customized via gitattributes, command line or a configuration. * "git diff" learned --patience to run "patience diff" algorithm. * "git filter-branch" learned --prune-empty option that discards commits that do not change the contents. * "git fsck" now checks loose objects in alternate object stores, instead of misreporting them as missing. * "git gc --prune" was resurrected to allow "git gc --no-prune" and giving non-default expiration period e.g. "git gc --prune=now". * "git grep -w" and "git grep" for fixed strings have been optimized. * "git mergetool" learned -y(--no-prompt) option to disable prompting. * "git rebase -i" can transplant a history down to root to elsewhere with --root option. * "git reset --merge" is a new mode that works similar to the way "git checkout" switches branches, taking the local changes while switching to another commit. * "git submodule update" learned --no-fetch option. * "git tag" learned --contains that works the same way as the same option from "git branch". Fixes since v1.6.1 ------------------ All of the fixes in v1.6.1.X maintenance series are included in this release, unless otherwise noted. Here are fixes that this release has, but have not been backported to v1.6.1.X series. * "git-add sub/file" when sub is a submodule incorrectly added the path to the superproject. * "git bundle" did not exclude annotated tags even when a range given from the command line wanted to. * "git filter-branch" unnecessarily refused to work when you had checked out a different commit from what is recorded in the superproject index in a submodule. * "git filter-branch" incorrectly tried to update a nonexistent work tree at the end when it is run in a bare repository. * "git gc" did not work if your repository was created with an ancient git and never had any pack files in it before. * "git mergetool" used to ignore autocrlf and other attributes based content rewriting. * branch switching and merges had a silly bug that did not validate the correct directory when making sure an existing subdirectory is clean. * "git -p cmd" when cmd is not a built-in one left the display in funny state when killed in the middle. GIT v1.6.1.4 Release Notes ========================== Fixes since v1.6.1.3 -------------------- * "git fast-export" produced wrong output with some parents missing from commits, when the history is clock-skewed. * "git fast-import" sometimes failed to read back objects it just wrote out and aborted, because it failed to flush stale cached data. * "git repack" did not error out when necessary object was missing in the repository. Also includes minor documentation fixes and updates. -- git shortlog --no-merges v1.6.1.3.. GIT v1.6.1.3 Release Notes ========================== Fixes since v1.6.1.2 -------------------- * "git diff --binary | git apply" pipeline did not work well when a binary blob is changed to a symbolic link. * Some combinations of -b/-w/--ignore-space-at-eol to "git diff" did not work as expected. * "git grep" did not pass the -I (ignore binary) option when calling out an external grep program. * "git log" and friends include HEAD to the set of starting points when --all is given. This makes a difference when you are not on any branch. * "git mv" to move an untracked file to overwrite a tracked contents misbehaved. * "git merge -s octopus" with many potential merge bases did not work correctly. * RPM binary package installed the html manpages in a wrong place. Also includes minor documentation fixes and updates. -- git shortlog --no-merges v1.6.1.2-33-gc789350.. --------------020703030901050602060901--