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:
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:
Add scmgit-gitk to meta package.
Bump PKGREVISION.

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.

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.

Log message:
Remove option scmgit-gui from devel/scmgit-base (++pkgrevision). Separate
"gitk" into individual package devel/scmgit-gitk.  Approved by wiz@.
Tested on RHEL.

Log message:
Changes 1.7.12:
UI, Workflows & Features
 * Git can be told to normalize pathnames it read from readdir(3) and
   all arguments it got from the command line into precomposed UTF-8
   (assuming that they come as decomposed UTF-8), in order to work
   around issues on Mac OS.
   I think there still are other places that need conversion
   (e.g. paths that are read from stdin for some commands), but this
   should be a good first step in the right direction.
 * Per-user $HOME/.gitconfig file can optionally be stored in
   $HOME/.config/git/config instead, which is in line with XDG.
 * The value of core.attributesfile and core.excludesfile default to
   $HOME/.config/git/attributes and $HOME/.config/git/ignore respectively
   when these files exist.
 * Logic to disambiguate abbreviated object names have been taught to
   take advantage of object types that are expected in the context,
   e.g. XXXXXX in the "git describe" output v1.2.3-gXXXXXX must be a
   commit object, not a blob nor a tree.  This will help us prolong
   the lifetime of abbreviated object names.
 * "git apply" learned to wiggle the base version and perform three-way
   merge when a patch does not exactly apply to the version you have.
 * Scripted Porcelain writers now have access to the credential API via
   the "git credential" plumbing command.
 * "git help" used to always default to "man" format even on \ 
platforms
   where "man" viewer is not widely available.
 * "git clone --local $path" started its life as an experiment to
   optionally use link/copy when cloning a repository on the disk, but
   we didn't deprecate it after we made the option a no-op to always
   use the optimization.  The command learned "--no-local" option to
   turn this off, as a more explicit alternative over use of file://
   URL.
 * "git fetch" and friends used to say "remote side hung up
   unexpectedly" when they failed to get response they expect from the
   other side, but one common reason why they don't get expected
   response is that the remote repository does not exist or cannot be
   read. The error message in this case was updated to give better
   hints to the user.
 * "git help -w $cmd" can show HTML version of documentation for
   "git-$cmd" by setting help.htmlpath to somewhere other than the
   default location where the build procedure installs them locally;
   the variable can even point at a http:// URL.
 * "git rebase [-i] --root $tip" can now be used to rewrite all the
   history leading to "$tip" down to the root commit.
 * "git rebase -i" learned "-x <cmd>" to insert \ 
"exec <cmd>" after
   each commit in the resulting history.
 * "git status" gives finer classification to various states of paths
   in conflicted state and offer advice messages in its output.
 * "git submodule" learned to deal with nested submodule structure
   where a module is contained within a module whose origin is
   specified as a relative URL to its superproject's origin.
 * A rather heavy-ish "git completion" script has been split to create
   a separate "git prompting" script, to help lazy-autoloading of the
   completion part while making prompting part always available.
 * "gitweb" pays attention to various forms of credits that are
   similar to "Signed-off-by:" lines in the commit objects and
   highlights them accordingly.