-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A new release of git, 1.6.1.2-1, has been uploaded. This replaces 1.6.0.4-1 as current.
NEWS: ===== This is a new upstream major release. I'm attaching the release notes; see also the package documentation in /usr/share/doc/git-1.6.1.2/. 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....@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 iEYEARECAAYFAkmNqwsACgkQ84KuGfSFAYDbdQCbBP0KdXeOtO3CUZbsnWfWqBSN UAsAn3m75ZdRoITmGfOAMx7u9bW5pzKC =N2Pr -----END PGP SIGNATURE-----
GIT v1.6.1.2 Release Notes ========================== Fixes since v1.6.1.1 -------------------- * The logic for rename detectin in internal diff used by commands like "git diff" and "git blame" have been optimized to avoid loading the same blob repeatedly. * We did not allow writing out a blob that is larger than 2GB for no good reason. * "git format-patch -o $dir", when $dir is a relative directory, used it as relative to the root of the work tree, not relative to the current directory. * v1.6.1 introduced an optimization for "git push" into a repository (A) that borrows its objects from another repository (B) to avoid sending objects that are available in repository B, when they are not yet used by repository A. However the code on the "git push" sender side was buggy and did not work when repository B had new objects that are not known by the sender. This caused pushing into a "forked" repository served by v1.6.1 software using "git push" from v1.6.1 sometimes did not work. The bug was purely on the "git push" sender side, and has been corrected. * "git status -v" did not paint its diff output in colour even when color.ui configuration was set. * "git ls-tree" learned --full-tree option to help Porcelain scripts that want to always see the full path regardless of the current working directory. * "git grep" incorrectly searched in work tree paths even when they are marked as assume-unchanged. It now searches in the index entries. * "git gc" with no grace period needlessly ejected packed but unreachable objects in their loose form, only to delete them right away. GIT v1.6.1.1 Release Notes ========================== Fixes since v1.6.1 ------------------ * "git add frotz/nitfol" when "frotz" is a submodule should have errored out, but it didn't. * "git apply" took file modes from the patch text and updated the mode bits of the target tree even when the patch was not about mode changes. * "git bisect view" on Cygwin did not launch gitk * "git checkout $tree" did not trigger an error. * "git commit" tried to remove COMMIT_EDITMSG from the work tree by mistake. * "git describe --all" complained when a commit is described with a tag, which was nonsense. * "git diff --no-index --" did not trigger no-index (aka "use git-diff as a replacement of diff on untracked files") behaviour. * "git format-patch -1 HEAD" on a root commit failed to produce patch text. * "git fsck branch" did not work as advertised; instead it behaved the same way as "git fsck". * "git log --pretty=format:%s" did not handle a multi-line subject the same way as built-in log listers (i.e. shortlog, --pretty=oneline, etc.) * "git daemon", and "git merge-file" are more careful when freopen fails and barf, instead of going on and writing to unopened filehandle. * "git http-push" did not like some RFC 4918 compliant DAV server responses. * "git merge -s recursive" mistakenly overwritten an untracked file in the work tree upon delete/modify conflict. * "git merge -s recursive" didn't leave the index unmerged for entries with rename/delete conflictd. * "git merge -s recursive" clobbered untracked files in the work tree. * "git mv -k" with more than one errorneous paths misbehaved. * "git read-tree -m -u" hence branch switching incorrectly lost a subdirectory in rare cases. * "git rebase -i" issued an unnecessary error message upon a user error of marking the first commit to be "squash"ed. * "git shortlog" did not format a commit message with multi-line subject correctly. Many documentation updates. GIT v1.6.1 Release Notes ======================== Updates since v1.6.0 -------------------- When some commands (e.g. "git log", "git diff") spawn pager internally, we used to make the pager the parent process of the git command that produces output. This meant that the exit status of the whole thing comes from the pager, not the underlying git command. We swapped the order of the processes around and you will see the exit code from the command from now on. (subsystems) * gitk can call out to git-gui to view "git blame" output; git-gui in turn can run gitk from its blame view. * Various git-gui updates including updated translations. * Various gitweb updates from repo.or.cz installation. * Updates to emacs bindings. (portability) * A few test scripts used nonportable "grep" that did not work well on some platforms, e.g. Solaris. * Sample pre-auto-gc script has OS X support. * Makefile has support for (ancient) FreeBSD 4.9. (performance) * Many operations that are lstat(3) heavy can be told to pre-execute necessary lstat(3) in parallel before their main operations, which potentially gives much improved performance for cold-cache cases or in environments with weak metadata caching (e.g. NFS). * The underlying diff machinery to produce textual output has been optimized, which would result in faster "git blame" processing. * Most of the test scripts (but not the ones that try to run servers) can be run in parallel. * Bash completion of refnames in a repository with massive number of refs has been optimized. * Cygwin port uses native stat/lstat implementations when applicable, which leads to improved performance. * "git push" pays attention to alternate repositories to avoid sending unnecessary objects. * "git svn" can rebuild an out-of-date rev_map file. (usability, bells and whistles) * When you mistype a command name, git helpfully suggests what it guesses you might have meant to say. help.autocorrect configuration can be set to a non-zero value to accept the suggestion when git can uniquely guess. * The packfile machinery hopefully is more robust when dealing with corrupt packs if redundant objects involved in the corruption are available elsewhere. * "git add -N path..." adds the named paths as an empty blob, so that subsequent "git diff" will show a diff as if they are creation events. * "git add" gained a built-in synonym for people who want to say "stage changes" instead of "add contents to the staging area" which amounts to the same thing. * "git apply" learned --include=paths option, similar to the existing --exclude=paths option. * "git bisect" is careful about a user mistake and suggests testing of merge base first when good is not a strict ancestor of bad. * "git bisect skip" can take a range of commits. * "git blame" re-encodes the commit metainfo to UTF-8 from i18n.commitEncoding by default. * "git check-attr --stdin" can check attributes for multiple paths. * "git checkout --track origin/hack" used to be a syntax error. It now DWIMs to create a corresponding local branch "hack", i.e. acts as if you said "git checkout --track -b hack origin/hack". * "git checkout --ours/--theirs" can be used to check out one side of a conflicting merge during conflict resolution. * "git checkout -m" can be used to recreate the initial conflicted state during conflict resolution. * "git cherry-pick" can also utilize rerere for conflict resolution. * "git clone" learned to be verbose with -v * "git commit --author=$name" can look up author name from existing commits. * output from "git commit" has been reworded in a more concise and yet more informative way. * "git count-objects" reports the on-disk footprint for packfiles and their corresponding idx files. * "git daemon" learned --max-connections=<count> option. * "git daemon" exports REMOTE_ADDR to record client address, so that spawned programs can act differently on it. * "git describe --tags" favours closer lightweight tags than farther annotated tags now. * "git diff" learned to mimic --suppress-blank-empty from GNU diff via a configuration option. * "git diff" learned to put more sensible hunk headers for Python, HTML and ObjC contents. * "git diff" learned to vary the a/ vs b/ prefix depending on what are being compared, controlled by diff.mnemonicprefix configuration. * "git diff" learned --dirstat-by-file to count changed files, not number of lines, when summarizing the global picture. * "git diff" learned "textconv" filters --- a binary or hard-to-read contents can be munged into human readable form and the difference between the results of the conversion can be viewed (obviously this cannot produce a patch that can be applied, so this is disabled in format-patch among other things). * "--cached" option to "git diff has an easier to remember synonym "--staged", to ask "what is the difference between the given commit and the contents staged in the index?" * "git for-each-ref" learned "refname:short" token that gives an unambiguously abbreviated refname. * Auto-numbering of the subject lines is the default for "git format-patch" now. * "git grep" learned to accept -z similar to GNU grep. * "git help" learned to use GIT_MAN_VIEWER environment variable before using "man" program. * "git imap-send" can optionally talk SSL. * "git index-pack" is more careful against disk corruption while completing a thin pack. * "git log --check" and "git log --exit-code" passes their underlying diff status with their exit status code. * "git log" learned --simplify-merges, a milder variant of --full-history; "gitk --simplify-merges" is easier to view than with --full-history. * "git log" learned "--source" to show what ref each commit was reached from. * "git log" also learned "--simplify-by-decoration" to show the birds-eye-view of the topology of the history. * "git log --pretty=format:" learned "%d" format element that inserts names of tags that point at the commit. * "git merge --squash" and "git merge --no-ff" into an unborn branch are noticed as user errors. * "git merge -s $strategy" can use a custom built strategy if you have a command "git-merge-$strategy" on your $PATH. * "git pull" (and "git fetch") can be told to operate "-v"erbosely or "-q"uietly. * "git push" can be told to reject deletion of refs with receive.denyDeletes configuration. * "git rebase" honours pre-rebase hook; use --no-verify to bypass it. * "git rebase -p" uses interactive rebase machinery now to preserve the merges. * "git reflog expire branch" can be used in place of "git reflog expire refs/heads/branch". * "git remote show $remote" lists remote branches one-per-line now. * "git send-email" can be given revision range instead of files and maildirs on the command line, and automatically runs format-patch to generate patches for the given revision range. * "git submodule foreach" subcommand allows you to iterate over checked out submodules. * "git submodule sync" subcommands allows you to update the origin URL recorded in submodule directories from the toplevel .gitmodules file. * "git svn branch" can create new branches on the other end. * "gitweb" can use more saner PATH_INFO based URL. (internal) * "git hash-object" learned to lie about the path being hashed, so that correct gitattributes processing can be done while hashing contents stored in a temporary file. * various callers of git-merge-recursive avoid forking it as an external process. * Git class defined in "Git.pm" can be subclasses a bit more easily. * We used to link GNU regex library as a compatibility layer for some platforms, but it turns out it is not necessary on most of them. * Some path handling routines used fixed number of buffers used alternately but depending on the call depth, this arrangement led to hard to track bugs. This issue is being addressed. Fixes since v1.6.0 ------------------ All of the fixes in v1.6.0.X maintenance series are included in this release, unless otherwise noted. * Porcelains implemented as shell scripts were utterly confused when you entered to a subdirectory of a work tree from sideways, following a symbolic link (this may need to be backported to older releases later). * Tracking symbolic links would work better on filesystems whose lstat() returns incorrect st_size value for them. * "git add" and "git update-index" incorrectly allowed adding S/F when S is a tracked symlink that points at a directory D that has a path F in it (we still need to fix a similar nonsense when S is a submodule and F is a path in it). * "git am" after stopping at a broken patch lost --whitespace, -C, -p and --3way options given from the command line initially. * "git diff --stdin" used to take two trees on a line and compared them, but we dropped support for such a use case long time ago. This has been resurrected. * "git filter-branch" failed to rewrite a tag name with slashes in it. * "git http-push" did not understand URI scheme other than opaquelocktoken when acquiring a lock from the server (this may need to be backported to older releases later). * After "git rebase -p" stopped with conflicts while replaying a merge, "git rebase --continue" did not work (may need to be backported to older releases). * "git revert" records relative to which parent a revert was made when reverting a merge. Together with new documentation that explains issues around reverting a merge and merging from the updated branch later, this hopefully will reduce user confusion (this may need to be backported to older releases later). * "git rm --cached" used to allow an empty blob that was added earlier to be removed without --force, even when the file in the work tree has since been modified. * "git push --tags --all $there" failed with generic usage message without telling saying these two options are incompatible. * "git log --author/--committer" match used to potentially match the timestamp part, exposing internal implementation detail. Also these did not work with --fixed-strings match at all. * "gitweb" did not mark non-ASCII characters imported from external HTML fragments correctly. GIT v1.6.0.6 Release Notes ========================== Fixes since 1.6.0.5 ------------------- * "git fsck" had a deep recursion that wasted stack space. * "git fast-export" and "git fast-import" choked on an old style annotated tag that lack the tagger information. * "git mergetool -- file" did not correctly skip "--" marker that signals the end of options list. * "git show $tag" segfaulted when an annotated $tag pointed at a nonexistent object. * "git show 2>error" when the standard output is automatically redirected to the pager redirected the standard error to the pager as well; there was no need to. * "git send-email" did not correctly handle list of addresses when they had quoted comma (e.g. "Lastname, Givenname" <m...@addre.ss>). * Logic to discover branch ancestry in "git svn" was unreliable when the process to fetch history was interrupted. * Removed support for an obsolete gitweb request URI, whose implementation ran "git diff" Porcelain, instead of using plumbing, which would have run an external diff command specified in the repository configuration as the gitweb user. Also contains numerous documentation typofixes. GIT v1.6.0.5 Release Notes ========================== Fixes since v1.6.0.4 -------------------- * "git checkout" used to crash when your HEAD was pointing at a deleted branch. * "git checkout" from an un-checked-out state did not allow switching out of the current branch. * "git diff" always allowed GIT_EXTERNAL_DIFF and --no-ext-diff was no-op for the command. * Giving 3 or more tree-ish to "git diff" is supposed to show the combined diff from second and subsequent trees to the first one, but the order was screwed up. * "git fast-export" did not export all tags. * "git ls-files --with-tree=<tree>" did not work with options other than -c, most notably with -m. * "git pack-objects" did not make its best effort to honor --max-pack-size option when a single first object already busted the given limit and placed many objects in a single pack. * "git-p4" fast import frontend was too eager to trigger its keyword expansion logic, even on a keyword-looking string that does not have closing '$' on the same line. * "git push $there" when the remote $there is defined in $GIT_DIR/branches/$there behaves more like what cg-push from Cogito used to work. * when giving up resolving a conflicted merge, "git reset --hard" failed to remove new paths from the working tree. * "git tag" did not complain when given mutually incompatible set of options. * The message constructed in the internal editor was discarded when "git tag -s" failed to sign the message, which was often caused by the user not configuring GPG correctly. * "make check" cannot be run without sparse; people may have meant to say "make test" instead, so suggest that. * Internal diff machinery had a corner case performance bug that choked on a large file with many repeated contents. * "git repack" used to grab objects out of packs marked with .keep into a new pack. * Many unsafe call to sprintf() style varargs functions are corrected. * Also contains quite a few documentation updates.
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
