|2013-06-16 09:40:22 by Adam Ciarcinski | Files touched by this commit (1)|
Log message: Remove PKGREVISION after updating to 22.214.171.124
|2013-06-16 08:31:12 by Adam Ciarcinski | Files touched by this commit (5) ||
Log message: Changes 126.96.36.199: * When $HOME is misconfigured to point at an unreadable directory, we used to complain and die. The check has been loosened. * Handling of negative exclude pattern for directories "!dir" was broken in the update to v1.8.3. Also contains a handful of trivial code clean-ups, documentation updates, updates to the test suite, etc.
|2013-06-10 13:40:10 by Greg Troxel | Files touched by this commit (2) ||
Log message: Update DESCR for gitk split.
|2013-05-15 13:16:29 by Adam Ciarcinski | Files touched by this commit (2) ||
Log message: Changes 188.8.131.52: * "rev-list --stdin" and friends kept bogus pointers into the input buffer around as human readable object names. This was not a huge problem but was exposed by a new change that uses these names in error output. * When "git difftool" drove "kdiff3", it mistakenly passed --auto option that was meant while resolving merge conflicts. * "git remote add" command did not diagnose extra command line arguments as an error and silently ignored them. Also contains a handful of trivial code clean-ups, documentation updates, updates to the test suite, etc.
|2013-04-11 13:46:22 by Adam Ciarcinski | Files touched by this commit (2) ||
Log message: Changes 184.108.40.206: * An earlier change to the attribute system introduced at v220.127.116.11 by mistake stopped a pattern "dir" (without trailing slash) from matching a directory "dir" (it only wanted to allow pattern \ "dir/" to also match). * Verification of signed tags were not done correctly when not in C or en/US locale. * 'git commit -m "$msg"' used to add an extra newline even when $msg already ended with one. * The "--match=<pattern>" option of "git describe", \ when used with "--all" to allow refs that are not annotated tags to be used as a base of description, did not restrict the output from the command to those that match the given pattern. * An aliased command spawned from a bare repository that does not say it is bare with "core.bare = yes" is treated as non-bare by mistake. * When "format-patch" quoted a non-ascii strings on the header files, it incorrectly applied rfc2047 and chopped a single character in the middle of it. * "git archive" reports a failure when asked to create an archive out of an empty tree. It would be more intuitive to give an empty archive back in such a case. * "git tag -f <tag>" always said "Updated tag \ '<tag>'" even when creating a new tag (i.e. not overwriting nor updating). * "git cmd -- ':(top'" was not diagnosed as an invalid syntax, and instead the parser kept reading beyond the end of the string. * Annotated tags outside refs/tags/ hierarchy were not advertised correctly to the ls-remote and fetch with recent version of Git. * The code to keep track of what directory names are known to Git on platforms with case insensitive filesystems can get confused upon a hash collision between these pathnames and looped forever. * The logic used by "git diff -M --stat" to shorten the names of files before and after a rename did not work correctly when the common prefix and suffix between the two filenames overlapped. * "git submodule update", when recursed into sub-submodules, did not acccumulate the prefix paths. * "git am $maildir/" applied messages in an unexpected order; sort filenames read from the maildir/ in a way that is more likely to sort messages in the order the writing MUA meant to, by sorting numeric segment in numeric order and non-numeric segment in alphabetical order. * When export-subst is used, "zip" output recorded incorrect size of the file. * Some platforms and users spell UTF-8 differently; retry with the most official "UTF-8" when the system does not understand the user-supplied encoding name that are the common alternative spellings of UTF-8. * "git branch" did not bother to check nonsense command line parameters and issue errors in many cases. * "git update-index -h" did not do the usual "-h(elp)" thing. * perl/Git.pm::cat_blob slurped everything in core only to write it out to a file descriptor, which was not a very smart thing to do. * The SSL peer verification done by "git imap-send" did not ask for Server Name Indication (RFC 4366), failing to connect SSL/TLS sites that serve multiple hostnames on a single IP. * "git index-pack" had a buffer-overflow while preparing an informational message when the translated version of it was too long. * Clarify in the documentation "what" gets pushed to \ "where" when the command line to "git push" does not say these explicitly. * In "git reflog expire", REACHABLE bit was not cleared from the correct objects. * The "--color=<when>" argument to the commands in the diff family was described poorly. * The arguments given to pre-rebase hook were not documented. * The v4 index format was not documented. * The "--match=<pattern>" argument "git describe" \ takes uses glob pattern but it wasn't obvious from the documentation. * Some sources failed to compile on systems that lack NI_MAXHOST in their system header (e.g. z/OS). * Add an example use of "--env-filter" in "filter-branch" documentation. * "git bundle verify" did not say "records a complete \ history" for a bundle that does not have any prerequisites. * In the v1.8.0 era, we changed symbols that do not have to be global to file scope static, but a few functions in graph.c were used by CGit from sideways bypassing the entry points of the API the in-tree users use. * "git merge-tree" had a typo in the logic to detect d/f conflicts, which caused it to segfault in some cases.
|2013-04-08 16:12:25 by Makoto Fujiwara | Files touched by this commit (6) ||
Log message: Bump scmgit version 18.104.22.168 to 1.8.2 Following packages are on this updates. devel/scmgit devel/scmgit-base devel/scmgit-docs devel/scmgit-gitk www/gitweb (nothing touched directly, but thanks gdt@) The release note for this version and its size are: wc devel/scmgit-base/work/git-1.8.2/RelNotes 495 3520 22140 devel/scmgit-base/work/git-1.8.2/RelNotes Files touched: -- devel/scmgit Makefile.version (GIT_VERSION 22.214.171.124 -> 1.8.2) -- devel/scmgit-base distinfo patches/patch-aa (part is moved to config.mak.uname) patches/patch-config.mak.uname (split from patch-aa) PLIST -- devel/scmgit-docs PLIST
|2013-03-23 20:00:31 by S.P.Zeidler | Files touched by this commit (4) ||
Log message: update gits version to one that fixes http://secunia.com/advisories/52361/ Changelogs: Fixes since v126.96.36.199 -------------------- * The attribute mechanism didn't allow limiting attributes to be applied to only a single directory itself with "path/" like the exclude mechanism does. The fix for this in 188.8.131.52 had performance degradations. * Command line completion code was inadvertently made incompatible with older versions of bash by using a newer array notation. * Scripts to test bash completion was inherently flaky as it was affected by whatever random things the user may have on $PATH. * A fix was added to the build procedure to work around buggy versions of ccache broke the auto-generation of dependencies, which unfortunately is still relevant because some people use ancient distros. * We used to stuff "user@" and then append what we read from /etc/mailname to come up with a default e-mail ident, but a bug lost the "user@" part. * "git am" did not parse datestamp correctly from Hg generated patch, when it is run in a locale outside C (or en). * Attempt to "branch --edit-description" an existing branch, while being on a detached HEAD, errored out. * "git cherry-pick" did not replay a root commit to an unborn branch. * We forgot to close the file descriptor reading from "gpg" output, killing "git log --show-signature" on a long history. * "git rebase --preserve-merges" lost empty merges in recent versions of Git. * Rebasing the history of superproject with change in the submodule has been broken since v1.7.12. * A failure to push due to non-ff while on an unborn branch dereferenced a NULL pointer when showing an error message. Also contains various documentation fixes. Fixes since v184.108.40.206 -------------------- * "git imap-send" talking over imaps:// did make sure it received a valid certificate from the other end, but did not check if the certificate matched the host it thought it was talking to. Also contains various documentation fixes. Fixes since v220.127.116.11 -------------------- * Given a string with a multi-byte character that begins with '-' on the command line where an option is expected, the option parser used just one byte of the unknown letter when reporting an error. * In v1.8.1, the attribute parser was tightened too restrictive to error out upon seeing an entry that begins with an ! (exclamation), which may confuse users to expect a "negative match", which does not exist. This has been demoted to a warning; such an entry is still ignored. * "git apply --summary" has been taught to make sure the similarity value shown in its output is sensible, even when the input had a bogus value. * "git clean" showed what it was going to do, but sometimes ended up finding that it was not allowed to do so, which resulted in a confusing output (e.g. after saying that it will remove an untracked directory, it found an embedded git repository there which it is not allowed to remove). It now performs the actions and then reports the outcome more faithfully. * "git clone" used to allow --bare and --separate-git-dir=$there options at the same time, which was nonsensical. * "git cvsimport" mishandled timestamps at DST boundary. * We used to have an arbitrary 32 limit for combined diff input, resulting in incorrect number of leading colons shown when showing the "--raw --cc" output. * The smart HTTP clients forgot to verify the content-type that comes back from the server side to make sure that the request is being handled properly. * "git help remote-helpers" failed to find the documentation. * "gitweb" pages served over HTTPS, when configured to show picon or gravatar, referred to these external resources to be fetched via HTTP, resulting in mixed contents warning in browsers. Also contains various documentation fixes.
|2013-01-30 18:39:39 by Adam Ciarcinski | Files touched by this commit (4)|
Log message: Changes 18.104.22.168: * An element on GIT_CEILING_DIRECTORIES list that does not name the real path to a directory (i.e. a symbolic link) could have caused the GIT_DIR discovery logic to escape the ceiling. * Command line completion for "tcsh" emitted an unwanted space after completing a single directory name. * Command line completion leaked an unnecessary error message while looking for possible matches with paths in <tree-ish>. * "git archive" did not record uncompressed size in the header when streaming a zip archive, which confused some implementations of unzip. * When users spelled "cc:" in lowercase in the fake "header" \ in the trailer part, "git send-email" failed to pick up the addresses from there. As e-mail headers field names are case insensitive, this script should follow suit and treat "cc:" and "Cc:" the \ same way.