SHA256
1
0
forked from pool/git

Accepting request 137467 from devel:tools:scm

Updated to 1.7.12.2 (forwarded request 137055 from douglarek)

OBS-URL: https://build.opensuse.org/request/show/137467
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/git?expand=0&rev=92
This commit is contained in:
Stephan Kulow 2012-10-10 07:19:20 +00:00 committed by Git OBS Bridge
parent 3e44f27794
commit b341d17a88
4 changed files with 44 additions and 4 deletions

View File

@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:a0c2b7e122ac2e40fe5b69baeeaac24b237a1341f08ba848cadaa835a0dbcfcd
size 4104575

3
git-1.7.12.2.tar.gz Normal file
View File

@ -0,0 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:1671b960dd761ef15d85f9be05d0b449b89f13ae39902082f9df865d85dac8aa
size 4106910

View File

@ -1,3 +1,43 @@
-------------------------------------------------------------------
Thu Oct 4 22:29:10 CST 2012 - douglarek@outlook.com
- updated to version 1.7.12.2:
* 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.
-------------------------------------------------------------------
Tue Sep 25 00:01:38 CST 2012 - douglarek@outlook.com

View File

@ -30,7 +30,7 @@ BuildRequires: perl-Error
BuildRequires: python
BuildRequires: sgml-skel
BuildRequires: xmlto
Version: 1.7.12.1
Version: 1.7.12.2
Release: 0
Summary: Fast, scalable, distributed revision control system
License: GPL-2.0