Log message:
Finish git rename from scmgit to git.

Log message:
Changes 1.8.4:
* Cygwin port has been updated for more recent Cygwin 1.7.
* "git rebase -i" now honors --strategy and -X options.
* Git-gui has been updated to its 0.18.0 version.
* MediaWiki remote helper (in contrib/) has been updated to use the
  credential helper interface from Git.pm.
* Update build for Cygwin 1.[57].  Torsten Bögershausen reports that
  this is fine with Cygwin 1.7 ($gmane/225824) so let's try moving it
  ahead.
* The credential helper to talk to keychain on OS X (in contrib/) has
  been updated to kick in not just when talking http/https but also
  imap(s) and smtp.
* Remote transport helper has been updated to report errors and
  maintain ref hierarchy used to keep track of its own state better.
* With "export" remote-helper protocol, (1) a push that tries to
  update a remote ref whose name is different from the pushing side
  does not work yet, and (2) the helper may not know how to do
  --dry-run; these problematic cases are disabled for now.
* git-remote-hg/bzr (in contrib/) updates.
* git-remote-mw (in contrib/) hints users to check the certificate,
  when https:// connection failed.
* git-remote-mw (in contrib/) adds a command to allow previewing the
  contents locally before pushing it out, when working with a
  MediaWiki remote.
Find more https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.4.txt

Log message:
Changes 1.8.3.1:
 * 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.

Log message:
Bump all packages for perl-5.18, that
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package

Like last time, where this caused no complaints.

Log message:
Bump scmgit version 1.8.1.5 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 1.8.1.5 -> 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

Log message:
update gits version to one that fixes http://secunia.com/advisories/52361/

Changelogs:

Fixes since v1.8.1.2
--------------------

 * 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 1.8.1.2 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 v1.8.1.3
--------------------

 * "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 v1.8.1.4
--------------------

 * 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.

Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

Log message:
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.