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:
Changes 1.8.2.3:
* "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.

Log message:
Changes 1.8.2.1:

 * An earlier change to the attribute system introduced at v1.8.1.2 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.

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:
PKGREVISION bumps for the security/openssl 1.0.1d update.

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

Log message:
Changes 1.8.1.1:
* The attribute mechanism didn't allow limiting attributes to be
  applied to only a single directory itself with "path/" like the
  exclude mechanism does.
* When attempting to read the XDG-style $HOME/.config/git/config and
  finding that $HOME/.config/git is a file, we gave a wrong error
  message, instead of treating the case as "a custom config file does
  not exist there" and moving on.
* After failing to create a temporary file using mkstemp(), failing
  pathname was not reported correctly on some platforms.
* http transport was wrong to ask for the username when the
  authentication is done by certificate identity.
* The behaviour visible to the end users was confusing, when they
  attempt to kill a process spawned in the editor that was in turn
  launched by Git with SIGINT (or SIGQUIT), as Git would catch that
  signal and die.  We ignore these signals now.
* A child process that was killed by a signal (e.g. SIGINT) was
  reported in an inconsistent way depending on how the process was
  spawned by us, with or without a shell in between.
* After "git add -N" and then writing a tree object out of the
  index, the cache-tree data structure got corrupted.
* "git apply" misbehaved when fixing whitespace breakages by removing
  excess trailing blank lines in some corner cases.
* A tar archive created by "git archive" recorded a directory in a
  way that made NetBSD's implementation of "tar" sometimes unhappy.
* When "git clone --separate-git-dir=$over_there" is interrupted, it
  failed to remove the real location of the $GIT_DIR it created.
  This was most visible when interrupting a submodule update.
* "git fetch --mirror" and fetch that uses other forms of refspec
  with wildcard used to attempt to update a symbolic ref that match
  the wildcard on the receiving end, which made little sense (the
  real ref that is pointed at by the symbolic ref would be updated
  anyway).  Symbolic refs no longer are affected by such a fetch.
* The "log --graph" codepath fell into infinite loop in some
  corner cases.
* "git merge" started calling prepare-commit-msg hook like "git
  commit" does some time ago, but forgot to pay attention to the exit
  status of the hook.
* "git pack-refs" that ran in parallel to another process that
  created new refs had a race that can lose new ones.
* When a line to be wrapped has a solid run of non space characters
  whose length exactly is the wrap width, "git shortlog -w" failed
  to add a newline after such a line.
* The way "git svn" asked for password using SSH_ASKPASS and
  GIT_ASKPASS was not in line with the rest of the system.
* "gitweb", when sorting by age to show repositories with new
  activities first, used to sort repositories with absolutely
  nothing in it early, which was not very useful.
* "gitweb", when sorting by age to show repositories with new
  activities first, used to sort repositories with absolutely
  nothing in it early, which was not very useful.
* When autoconf is used, any build on a different commit always ran
  "config.status --recheck" even when unnecessary.
* Some scripted programs written in Python did not get updated when
  PYTHON_PATH changed.
* We have been carrying a translated and long-unmaintained copy of an
  old version of the tutorial; removed.
* Portability issues in many self-test scripts have been addressed.

Log message:
Changed 1.8.0.1
* The configuration parser had an unnecessary hardcoded limit on
  variable names that was not checked consistently.
* The "say" function in the test scaffolding incorrectly allowed
  "echo" to interpret "\a" as if it were a C-string asking for a
  BEL output.
* "git mergetool" feeds /dev/null as a common ancestor when dealing
  with an add/add conflict, but p4merge backend cannot handle
  it. Work it around by passing a temporary empty file.
* "git log -F -E --grep='<ere>'" failed to use the given <ere>
  pattern as extended regular expression, and instead looked for the
  string literally.
* "git grep -e pattern <tree>" asked the attribute system to read
  "<tree>:.gitattributes" file in the working tree, which was
  nonsense.
* A symbolic ref refs/heads/SYM was not correctly removed with "git
  branch -d SYM"; the command removed the ref pointed by SYM
  instead.
* Earlier we fixed documentation to hyphenate "remote-tracking branch"
  to clarify that these are not a remote entity, but unhyphenated
  spelling snuck in to a few places since then.
* "git pull --rebase" run while the HEAD is detached tried to find
  the upstream branch of the detached HEAD (which by definition
  does not exist) and emitted unnecessary error messages.
* The refs/replace hierarchy was not mentioned in the
  repository-layout docs.
* Sometimes curl_multi_timeout() function suggested a wrong timeout
  value when there is no file descriptors to wait on and the http
  transport ended up sleeping for minutes in select(2) system call.
  A workaround has been added for this.
* Various rfc2047 quoting issues around a non-ASCII name on the
  From: line in the output from format-patch have been corrected.
* "git diff -G<pattern>" did not honor textconv filter when looking
  for changes.
* Bash completion script (in contrib/) did not correctly complete a
  lazy "git checkout $name_of_remote_tracking_branch_that_is_unique"
  command line.
* RSS feed from "gitweb" had a xss hole in its title output.
* "git config --path $key" segfaulted on "[section] key" (a \ 
boolean
  "true" spelled without "=", not "[section] key = \ 
true").
* "git checkout -b foo" while on an unborn branch did not say
  "Switched to a new branch 'foo'" like other cases.
Also contains other minor fixes and documentation updates.

Log message:
Changes 1.8.0:
UI, Workflows & Features
 * A credential helper for Win32 to allow access to the keychain of
   the logged-in user has been added.
 * An initial port to HP NonStop.
 * A credential helper to allow access to the Gnome keyring has been
   added.
 * When "git am" sanitizes the "Subject:" line, we strip the \ 
prefix from
   "Re: subject" and also from a less common "re: subject", \ 
but left
   the even less common "RE: subject" intact.  Now we strip that too.
 * It was tempting to say "git branch --set-upstream origin/master",
   but that tells Git to arrange the local branch "origin/master" to
   integrate with the currently checked out branch, which is highly
   unlikely what the user meant.  The option is deprecated; use the
   new "--set-upstream-to" (with a short-and-sweet "-u") option
   instead.
 * "git cherry-pick" learned the "--allow-empty-message" \ 
option to
   allow it to replay a commit without any log message.
 * After "git cherry-pick -s" gave control back to the user asking
   help to resolve conflicts, concluding "git commit" used to need to
   be run with "-s" if the user wants to sign it off; now the command
   leaves the sign-off line in the log template.
 * "git daemon" learned the "--access-hook" option to allow an
   external command to decline service based on the client address,
   repository path, etc.
 * "git difftool --dir-diff" learned to use symbolic links to prepare
   a temporary copy of the working tree when available.
 * "git grep" learned to use a non-standard pattern type by default if
   a configuration variable tells it to.
 * Accumulated updates to "git gui" has been merged.
 * "git log -g" learned the "--grep-reflog=<pattern>" \ 
option to limit
   its output to commits with a reflog message that matches the given
   pattern.
 * "git merge-base" learned the "--is-ancestor A B" option \ 
to tell if A is
   an ancestor of B.  The result is indicated by its exit status code.
 * "git mergetool" now allows users to override the actual command used
   with the mergetool.$name.cmd configuration variable even for built-in
   mergetool backends.
 * "git rebase -i" learned the "--edit-todo" option to open \ 
an editor
   to edit the instruction sheet.