gitk-2.13.7-16.1<>,7[y/=„rzHqPsѠ$%,Yq[9ZեsG,\Iz"kCR~=RLT d^+s5~}Ԥ;C3`#Y '8Y* VAAL~{ ]xsd֋!< rENJo97:=OrAΰ-{=o.M&6~w]d9B[D;nMprPwaLGW*=!9w+f.bc= 3n2>=?d  0@DLPcly  @ d   R  8(89 :OFGH(IpXY\]^jbcwdef lu$vlw<xyzCgitk2.13.716.1Git revision tree visualiserGrapical tool for visualization of revision trees of projects maintained in the Git version control system. It name gitk indicates that it's written using the Tk Widget set. A simple Tk based graphical interface for common Git operations is found in the package git-gui.[ylamb21 }openSUSE Leap 42.3openSUSEGPL-2.0-onlyhttp://bugs.opensuse.orgDevelopment/Tools/Version Controlhttp://git-scm.comlinuxx86_64]e,d{91g;^lT&Yfb*~ AAA큤[x{[x{[x{[x{[x{[x{[x{[x{[x{[x{[x{[x{[x{[x{[x{[x{[x{[xzc3b08b3ed628db63a3039f12afb81cbdf8675538ec8be29cd1afc19325e698445e5819860e6ed674518b51f99518890c42c4f07fd233025d875dd94dfdcd9857cbc95fea6b9e243b446c188ed7a1e07230b22d49116e79a7f03127ed9b7dcbb0d3897f5383ee73f86b8f42115e9b862e803f07984eea91aad390280355948e75bd9adf4afeceab9a3b52a237c8e3b9809f2951008eb467110b926280d95083f6aefc29209603ad0871d200f7b93be7f6878b6d3e5a84a3eb749397c887c43ab54fea140895208535bfd9e1611635b8c460ca48be37b64bbad3e1f994e2d224d4b20c5347fd2888c45c64c5a050f55c7erootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootgit-2.13.7-16.1.src.rpmgitkgitk(x86-64)@   /bin/shgit-corerpmlib(CompressedFileNames)rpmlib(PayloadFilesHavePrefix)tkrpmlib(PayloadIsLzma)2.13.73.0.4-14.0-18.44.4.6-14.11.2[F[@Za@YA@YJYYg`YOY5GY)j@YYX[XXXqXYXpXXJX>@X@WW@Wʻ@WW W!WW^@WV@W=W$@W@WVbV@V@VIVV@V_V@V@V@VhV=V(V$@VV }@V7@UUN@U@U@UXUnUnUU@U>Ua@Ut2@UeUT@UG_@U?v@U<@UUQU"UT@TT TԬTT@Tw@Tk4Ti@TPT+T*@Tl@S@S/SӘ@S@SQ@S-SDSof@SJ|@S,)S@R'R>R&RRRRv@Rv@RRiRpRe@R' RC@RQ@Q@QJQxQQ@QIQQzl@Qb@Q\QT0QT0QAQ?Q$QtQ @PPPP@P5@P@PvPr@PnPaPPy@PO'P,P!@OOĺ@O@OKp@O3@O"O yN>@NN@NNN$@N@Ni@NyNV9@N NpN|@MAM@Mߒ@Mx@MfH@MZjM PM L@L{Lnn@LQm@LH2L@K@KՀ@K@KK[KK@Kf@KK{@Ky7@KXAK+nK?K@JJ@JJ@JJ?r@J)JIcII?@Itiwai@suse.detiwai@suse.detiwai@suse.deastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comschwab@linux-m68k.orgastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comlchiquitto@suse.deastieger@suse.comdimstar@opensuse.orgastieger@suse.comlchiquitto@suse.deolaf@aepfle.deastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comolaf@aepfle.deastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comtermim@gmail.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.combwiedemann@suse.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comtiwai@suse.deastieger@suse.comastieger@suse.comastieger@suse.comtiwai@suse.deastieger@suse.comdimstar@opensuse.orgastieger@suse.comastieger@suse.comschwab@suse.deastieger@suse.comastieger@suse.comjslaby@suse.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comjengelh@inai.deastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comastieger@suse.comtiwai@suse.deastieger@suse.comschwab@linux-m68k.orgastieger@suse.comastieger@suse.comandreas.stieger@gmx.deandreas.stieger@gmx.deandreas.stieger@gmx.denovell@mirell.debwiedemann@suse.comandreas.stieger@gmx.debwiedemann@suse.comandreas.stieger@gmx.deandreas.stieger@gmx.deandreas.stieger@gmx.deandreas.stieger@gmx.deandreas.stieger@gmx.deandreas.stieger@gmx.deandreas.stieger@gmx.deandreas.stieger@gmx.deandreas.stieger@gmx.deandreas.stieger@gmx.deandreas.stieger@gmx.deburnus@net-b.deburnus@net-b.detiwai@suse.dejengelh@inai.deiartarisi@suse.comdouglarek@outlook.comohering@suse.detiwai@suse.detiwai@suse.dedouglarek@outlook.comdouglarek@outlook.comdouglarek@outlook.comdouglarek@outlook.comdouglarek@outlook.comtiwai@suse.dedouglarek@outlook.comdouglarek@outlook.comdouglarek@outlook.comdouglarek@outlook.comdouglarek@outlook.comdouglarek@outlook.compgajdos@suse.comschwab@linux-m68k.orgdouglarek@outlook.comspeilicke@suse.compgajdos@suse.comdouglarek@outlook.comtiwai@suse.dejengelh@inai.delchiquitto@suse.comdouglarek@outlook.comdouglarek@outlook.comtiwai@suse.dedouglarek@outlook.comdouglarek@outlook.comdouglarek@outlook.comdouglarek@outlook.comdouglarek@outlook.comdouglarek@outlook.comdouglarek@outlook.comdouglarek@outlook.comdouglarek@outlook.comschwab@linux-m68k.orgdouglarek@outlook.comdouglarek@outlook.comfrank.lichtenheld@sophos.comtiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.defrank.lichtenheld@sophos.comsaschpe@suse.detiwai@suse.dejpschewe@mtu.netidonmez@suse.comidonmez@suse.comtiwai@suse.detiwai@suse.decfarrell@suse.comtiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.dedmueller@suse.dechris@computersalat.detiwai@suse.decoolo@novell.comdmueller@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.depbaudis@suse.czchris@computersalat.detiwai@suse.dedmueller@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.dejengelh@medozas.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.deopensuse@sukimashita.comlnussel@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.detiwai@suse.de- Fix VUL-0: arbitrary code execution via .gitmodules (CVE-2018-17456, bsc#1110949): 0001-submodule-helper-use-to-signal-end-of-clone-options.patch 0002-submodule-config-ban-submodule-urls-that-start-with-.patch 0003-submodule-config-ban-submodule-paths-that-start-with.patch- Update to git 2.13.7: security fix release * path sanity-checks on NTFS can read arbitrary memory (CVE-2018-11233, bsc#1095218) * arbitrary code execution when recursively cloning a malicious repository (CVE-2018-11235, bsc#1095219)- Fix mishandling layers of tree objects, which allows remote attackers to cause DoS a crafted repository, aka a Git bomb (CVE-2017-15298, bsc#1063412): git-CVE-2017-15298.patch- git 2.13.6: * Various Perl scripts did not use safe_pipe_capture() instead of backticks, leaving them susceptible to end-user input. CVE-2017-14867 bsc#1061041 * "git cvsserver" no longer is invoked by "git daemon" by default- git 2.13.5 (bsc#1052481): * Security fix for CVE-2017-1000117: A malicious third-party can give a crafted "ssh://..." URL to an unsuspecting victim, and an attempt to visit the URL can result in any program that exists on the victim's machine being executed. Such a URL could be placed in the .gitmodules file of a malicious project, and an unsuspecting victim could be tricked into running "git clone --recurse-submodules" to trigger the vulnerability. * A "ssh://..." URL can result in a "ssh" command line with a hostname that begins with a dash "-", which would cause the "ssh" command to instead (mis)treat it as an option. This is now prevented by forbidding such a hostname (which should not impact any real-world usage). * Similarly, when GIT_PROXY_COMMAND is configured, the command is run with host and port that are parsed out from "ssh://..." URL; a poorly written GIT_PROXY_COMMAND could be tricked into treating a string that begins with a dash "-" as an option. This is now prevented by forbidding such a hostname and port number (again, which should not impact any real-world usage). * In the same spirit, a repository name that begins with a dash "-" is also forbidden now.- git 2.13.4: * Update the character width tables. * Fix an alias that contained an uppercase letter * Progress meter fixes * git gc concurrency fixes- git 2.13.3: * various internal bug fixes * Fix a regression to "git rebase -i" * Correct unaligned 32-bit access in pack-bitmap code * Tighten error checks for invalid "git apply" input * The split index code did not honor core.sharedrepository setting correctly * Fix "git branch --list" handling of color.branch.local- git 2.13.2: * "collision detecting" SHA-1 update for platform fixes * "git checkout --recurse-submodules" did not quite work with a submodule that itself has submodules. * The "run-command" API implementation has been made more robust against dead-locking in a threaded environment. * "git clean -d" now only cleans ignored files with "-x" * "git status --ignored" did not list ignored and untracked files without "-uall" * "git pull --rebase --autostash" didn't auto-stash when the local history fast-forwards to the upstream. * "git describe --contains" gives as much weight to lightweight tags as annotated tags * Fix "git stash push " from a subdirectory- git 2.13.1: * Setting "log.decorate=false" in the configuration file did not take effect in v2.13, which has been corrected. * corrections to documentation and command help output * garbage collection fixes * memory leaks fixed * receive-pack now makes sure that the push certificate records the same set of push options used for pushing * shell completion corrections for git stash * fix "git clone --config var=val" with empty strings * internal efficiency improvements * Update sha1 collision detection code for big-endian platforms and platforms not supporting unaligned fetches- Fix packaging of documentation- git 2.13.0: * empty string as a pathspec element for 'everything matches' is still warned, for future removal. * deprecated argument order "git merge HEAD ..." was removed * default location "~/.git-credential-cache/socket" for the socket used to communicate with the credential-cache daemon moved to "~/.cache/git/credential/socket". * now avoid blindly falling back to ".git" when the setup sequence indicated otherwise * many workflow features, improvements and bug fixes * add a hardened implementation of SHA1 in response to practical collision attacks (CVE-2005-4900, bsc#1042640)- git 2.12.3: * CVE-2017-8386: On a server running git-shell as login shell to restrict user to git commands, remote users may have been able to have git service programs spawn an interactive pager and thus escape the shell restrictions. (bsc#1038395)- git 2.12.2: * CLI output fixes * "Dump http" transport fixes * various fixes for internal code paths * Trailer "Cc:" RFC fix- git 2.12.1: * Reduce authentication round-trip over HTTP when the server supports just a single authentication method. * "git add -i" patch subcommand fixed to have a path selection * various path verification fixes * fix "git log -L..." buffer overrun- Submit version 2.12.0 to SLE-12 (fate#322294, bsc#977477)- git 2.12.0: * Use of an empty string that is used for 'everything matches' is still warned and Git asks users to use a more explicit '.' for that instead. The hope is that existing users will not mind this change, and eventually the warning can be turned into a hard error, upgrading the deprecation into removal of this (mis)feature. That is not scheduled to happen in the upcoming release (yet). * The historical argument order "git merge HEAD ..." has been deprecated for quite some time, and will be removed in a future release. * An ancient script "git relink" has been removed.- Explicitly package %{_docdir}/%{name} to fix build with RPM 4.13.- git 2.11.1: * The default Travis-CI configuration specifies newer P4 and GitLFS. * The character width table has been updated to match Unicode 9.0 * various fixes affecting multiple subcommands for correctness, bugs, and unexpected behavior. * documentation updates * git-svn updates- Refresh all patches to update line numbers - Add old bug reference to allow submission to SLE-12- git-gui: Sort entries in optimized tclIndex git-gui-tclIndex.patch- git 2.11.0: * backward compatibility: + empty string (matching everything) used as pathspec now triggers a warning + historical argument order "git merge HEAD ..." is deprecated + default abbreviation length of 7 now scales by repo size * updates + new version of git-gui + many new command line and configuration options + many workflow and output improvements * dropped upstreamed patches: + git-setup-i18n-fix.patch + git-tclIndex.patch- git 2.10.2: * minor bug fixes * internal code improvements * documentation updates- git 2.10.1: * documentation and command output updates * Prevents loops on submodules with broken metadata * Forbid removal of the symbolic reference HEAD * Update Japanese translation for "git-gui". * Fix "git commit-tree" reading commit.gpgsign configuration * Ignore merges when matching with "git log --cherry-pick" * Fix "git format-patch --base=..." usage of signature separator * "git add --chmod=+x " added recently only toggled the executable bit for paths that are either new or modified. This has been corrected to flip the executable bit for all paths that match the given pathspec.- fix shell lib include path in git-sh-setup (boo#1011169) adding git-setup-i18n-fix.patch- git 2.10.0, feature and bugfix update: * various workflow output improvements * various improvements and extensions of command line options * A handful of "git svn" updates. * internal performance improvements- Reduce build-compare noise git-asciidoc.patch git-tclIndex.patch- git 2.9.3: * many compatible fixes and improvements to various git commands and functions- git 2.9.2: * fix test suite failues with 64 bit timestamps- git 2.9.1: * socket-level KEEPALIVE for git daemon * Various compatible workflow and UI fixes * Various optimisations and documentation updates * Fix regression in v2.9 affecting "clone --depth"- git 2.9.0: * commands in the "git diff" and "git log" family by default enable the rename detection; use "diff.renames" configuration variable to disable this. * merging two branches that have no common ancestor with "git merge" is by default forbidden now to prevent creating such an unusual merge by mistake. * output formats of "git log" that indents the commit log message by 4 spaces now expands HT in the log message by default. The "--no-expand-tabs" option disables this. * "git commit-tree" plumbing command required the user to always sign its result when the user sets the commit.gpgsign configuration variable, this is no longer the case. Scrips using commit-tree which may rely on this mistake no needs to read commit.gpgsign and pass the -S option as necessary. * Many more bug fixes and minor updates.- git 2.8.4: * Documentation updates * "git fsck" learned to catch NUL byte in a commit object as potential error and warn. * "git describe --contains" improvements * Treat "http.cookieFile" config as a path * Suggest "submodule deinit --all" for deinitializing all submodules * A couple of bugs around core.autocrlf have been fixed. * "git difftool" learned to handle unmerged paths correctly in dir-diff mode.- git 2.8.3: * "git send-email" now uses a more readable timestamps when formulating a message ID. * When "git worktree" feature is in use, "git branch -d" allowed deletion of a branch that is checked out in another worktree * When "git worktree" feature is in use, "git branch -m" renamed a branch that is checked out in another worktree without adjusting the HEAD symbolic ref for the worktree. * "git format-patch --help" showed `-s` and `--no-patch` as if these are valid options to the command. We already hide `--patch` option from the documentation, because format-patch is about showing the diff, and the documentation now hides these options as well. * A change back in version 2.7 to "git branch" broke display of a symbolic ref in a non-standard place in the refs/ hierarchy (we expect symbolic refs to appear in refs/remotes/*/HEAD to point at the primary branch the remote has, and as .git/HEAD to point at the branch we locally checked out). * A partial rewrite of "git submodule" in the 2.7 timeframe changed the way the gitdir: pointer in the submodules point at the real repository location to use absolute paths by accident. This has been corrected. * "git commit" misbehaved in a few minor ways when an empty message is given via -m '', all of which has been corrected. * Support for CRAM-MD5 authentication method in "git imap-send" did not work well. * The socks5:// proxy support added back in 2.6.4 days was not aware that socks5h:// proxies behave differently. * "git config" had a codepath that tried to pass a NULL to printf("%s"), which nobody seems to have noticed. * "git replace -e" did not honour "core.editor" configuration. * "git submodule" reports the paths of submodules the command recurses into, but this was incorrect when the command was not run from the root level of the superproject. * The "user.useConfigOnly" configuration variable makes it an error if users do not explicitly set user.name and user.email. However, its check was not done early enough and allowed another error to trigger, reporting that the default value we guessed from the system setting was unusable. This was a suboptimal end-user experience as we want the users to set user.name/user.email without relying on the auto-detection at all. * "git mv old new" did not adjust the path for a submodule that lives as a subdirectory inside old/ directory correctly. * "git push" from a corrupt repository that attempts to push a large number of refs deadlocked; the thread to relay rejection notices for these ref updates blocked on writing them to the main thread, after the main thread at the receiving end notices that the push failed and decides not to read these notices and return a failure. * A question by "git send-email" to ask the identity of the sender has been updated. * Recent update to Git LFS broke "git p4" by changing the output from its "lfs pointer" subcommand. * Some multi-byte encoding can have a backslash byte as a later part of one letter, which would confuse "highlight" filter used in gitweb.- git 2.8.2: * "index-pack --keep=" was broken since v2.1.0 timeframe. * "git config --get-urlmatch", unlike other variants of the "git config --get" family, did not signal error with its exit status when there was no matching configuration. * The "--local-env-vars" and "--resolve-git-dir" options of "git rev-parse" failed to work outside a repository when the command's option parsing was rewritten in 1.8.5 era. * Fetching of history by naming a commit object name directly didn't work across remote-curl transport. * A small memory leak in an error codepath has been plugged in xdiff code. * "git mergetool" did not work well with conflicts that both sides deleted. * "git send-email" had trouble parsing alias file in mailrc format when lines in it had trailing whitespaces on them. * When "git merge --squash" stopped due to conflict, the concluding "git commit" failed to read in the SQUASH_MSG that shows the log messages from all the squashed commits. * "git merge FETCH_HEAD" dereferenced NULL pointer when merging nothing into an unborn history (which is arguably unusual usage, which perhaps was the reason why nobody noticed it). * "git diff -M" used to work better when two originally identical files A and B got renamed to X/A and X/B by pairing A to X/A and B to X/B, but this was broken in the 2.0 timeframe. * "git send-pack --all " was broken when its command line option parsing was written in the 2.6 timeframe. * When running "git blame $path" with unnormalized data in the index for the path, the data in the working tree was blamed, even though "git add" would not have changed what is already in the index, due to "safe crlf" that disables the line-end conversion. It has been corrected.- add desktop entry for the git gui- git 2.8.1: * make rpmbuild target was broken, unused in openSUSE package- git 2.8.0 * Backward compatibility: + The rsync:// transport has been removed. * various subcommands improvements * various output improvements * improved handling of notes * improved handling of end of line styles * http.proxyAuthMethod configures proxy authentication method * new "^{/!-}" notation * "user.useConfigOnly" configuration variable forces individual project configuration * "git fetch" and friends that make network connections can now be told to only use ipv4 (or ipv6). * http.[.]pinnedpubkey to specify the pinned public key * bug fixes and performance improvements- git 2.7.4: Fix remote code execution via buffer overflow (CVE-2016-2315, CVE-2016-2324, bsc#971328) * plug heap corruption holes * catch integer overflow in the computation of pathname lengths * get rid of the name_path API. Both of These would have resulted in writing over an under-allocated buffer when formulating pathnames while tree traversal.- git 2.7.3: * "git show 'HEAD:Foo[BAR]Baz'" did not interpret the argument as a rev, i.e. the object named by the the pathname with wildcard characters in a tree object. * "git rev-parse --git-common-dir" used in the worktree feature misbehaved when run from a subdirectory. * The "v(iew)" subcommand of the interactive "git am -i" command was broken in 2.6.0 timeframe when the command was rewritten in C. * "git merge-tree" used to mishandle "both sides added" conflict with its own "create a fake ancestor file that has the common parts of what both sides have added and do a 3-way merge" logic; this has been updated to use the usual "3-way merge with an empty blob as the fake common ancestor file" approach used in the rest of the system. * The documentation did not clearly state that the 'simple' mode is now the default for "git push" when push.default configuration is not set. * Test adjustments for GNU grep, obsoleting git-2.7.1-fix-tests-grep-2.23.patch * "git config section.var value" to set a value in per-repository configuration file failed when it was run outside any repository, but didn't say the reason correctly.- git 2.7.2: * improvements placing conflict markers with different line terminators * "git worktree" fixes for manually moved paths * "git push --force-with-lease" has been taught to report if the push needed to force (or fast-forwarded). * vimdiff backend improvements for "git mergetool": buffer order * improvements for handling paths added to index with "add -N" which are not in the index yet- fix test failures with grep 2.23 add git-2.7.1-fix-tests-grep-2.23.patch- git 2.7.1: * fix hooks and aliases fixes with GIT_WORK_TREE * fix "git send-email" reading escaped quotes in mutt alias files * fix some crashes and regressions- use %perl_requires to allow for easier git+perl updates (boo#961112)- package git-new-workdir [boo#961292]- git 2.7.0: * UI, Workflows & Features updates * new subcommands, parameters and configuration options * performance improvements and code clean-ups * remove upstreamed patches: 0001-gitk-Fix-crash-with-all-in-non-English-locales.patch 0002-gitk-Update-msgid-s-for-menu-items-with-accelerator.patch 0003-gitk-Add-accelerators-to-Japanese-locale.patch 0004-gitk-Add-accelerator-to-German-locale.patch- git 2.6.5: * Update "git subtree" (in contrib/) so that it can take whitespaces in the pathnames, not only in the in-tree pathname but the name of the directory that the repository is in. * "git p4" used to import Perforce CLs that touch only paths outside the client spec as empty commits. It has been corrected to ignorethem instead, with a new configuration git-p4.keepEmptyCommits as a backward compatibility knob. * Improve error reporting when SMTP TLS fails. * "git symbolic-ref" forgot to report a failure with its exit status. * History traversal with "git log --source" that starts with an annotated tag failed to report the tag as "source", due to an old regression in the command line parser back in v2.2 days.- git 2.6.4: * Add support for talking http/https over socks proxy. * Allow all hooks to ignore their standard input, rather than having git complain of SIGPIPE. * Allow tilde-expansion in some http config variables. * Make git-p4 work on a detached head. * Add "git rebase --no-autostash" * Allow "git interpret-trailers" to run outside of a Git repository.- git 2.6.3: * UI output fixes * Bug fixes on case insensitive filesystems * git p4 fixes * Prepare for Git on-disk repository representation to undergo backward incompatible changes by introducing a new repository format version "1", with an extension mechanism. - include gpg2 for tests- Fix crash of gitk with --all option in non-English locales (bsc#951153): 0001-gitk-Fix-crash-with-all-in-non-English-locales.patch 0002-gitk-Update-msgid-s-for-menu-items-with-accelerator.patch 0003-gitk-Add-accelerators-to-Japanese-locale.patch 0004-gitk-Add-accelerator-to-German-locale.patch- git 2.6.2: * git fsck return status fixes * Fix for case insensitive filesystems * Fix "git am" ignoring user.signingkey * For ssh transport, explicitly clear GIT_* environment variables * Other compatible minor bug fixes and improvements - drop pager-don-t-use-unsafe-functions-in-signal-handle.patch- git 2.6.1, with a security fix: * Make xdiff code handle extremely large files, cap around 1GB. * Some protocols (like git-remote-ext) can execute arbitrary code found in the URL. The URLs that submodules use may come from arbitrary sources (e.g., .gitmodules files in a remote repository), and can hurt those who blindly enable recursive fetch. Restrict the allowed protocols to well known and safe ones. [boo#948969]- git 2.6.0: * many UI and workflow updates, added parameters and options * some performance optimisations and resource use reduction - refresh pager-don-t-use-unsafe-functions-in-signal-handle.patch- Fix deadlock in signal handler in pager (boo#942297): pager-don-t-use-unsafe-functions-in-signal-handle.patch- git 2.5.3: * The experimental untracked-cache feature were buggy when paths with a few levels of subdirectories are involved. * Fix performance regression in "git am --skip"- Suggest instead of recommend git-web: git-web is the web-server browsing part. Users that install git-core and appache will still get it auto-recommended based on the supplements.- git 2.5.2: * usability bug fixes * performance bug fixes * fix "git archive" usage of zip64 for >64k entries- git 2.5.1: * Performance optimisation for some casee * Minor bug fixes * Fix a regression for clone repository name guessing * Fix a regressoin in "git pull" related to --upload-pack- In SLE 11 perl-Term-ReadKey is called perl-TermReadKey- git 2.5.0: * Improvements working with perforce (git p4) * A new short-hand @{push} * Introduce http..SSLCipherList configuration variable to tweak the list of cipher suite to be used with libcURL when talking with https:// sites. * "git cat-file --batch(-check)" new option "--follow-symlinks" * "git send-email" learned the alias file format used by the sendmail program * For 3-way merge drivers, add %P (final path) * "git blame" learned blame.showEmail configuration variable. * Add the "--allow-unknown-type" option to "cat-file" * Many long-running operations now show progress eye-candy- git 2.4.7: * Fix "git fsck" regression related to body-less tag object * Ask libCURL to use the most secure proxy authentication method * Fix shell handling issues in git log * Fix git config on read-only fs * Make "git rebase" exit with failure when format-patch fails- put git-credential-cache--daemon into git-core -- it is needed for git-credential-cache (bnc#939065)- git 2.4.6: * "git fetch --depth=" and "git clone --depth=" issued a shallow transfer request even to an upload-pack that does not support the capability. * "git fsck" used to ignore missing or invalid objects recorded in reflog. * The tcsh completion writes a bash scriptlet but that would have failed for users with noclobber set. * "git format-patch --ignore-if-upstream A..B" did not like to be fed tags as boundary commits. - git-tcsh-completion-fixes.diff adjusted for context changes- git 2.4.5: * internal code and stability improvements * ""git rebase -i" fired post-rewrite hook when it shouldn't (namely, when it was told to stop sequencing with 'exec' insn).- git 2.4.4: * l10n updates for German. * An earlier leakfix to bitmap testing code was incomplete. * "git clean pathspec..." tried to lstat(2) and complain even for paths outside the given pathspec. * Communication between the HTTP server and http_backend process can lead to a dead-lock when relaying a large ref negotiation request. Diagnose the situation better, and mitigate it by reading such a request first into core (to a reasonable limit). * The clean/smudge interface did not work well when filtering an empty contents (failed and then passed the empty input through). It can be argued that a filter that produces anything but empty for an empty input is nonsense, but if the user wants to do strange things, then why not? * Make "git stash something --help" error out, so that users can safely say "git stash drop --help". * Clarify that "log --raw" and "log --format=raw" are unrelated concepts. * Catch a programmer mistake to feed a pointer not an array to ARRAY_SIZE() macro, by using a couple of GCC extensions.- git 2.4.3: * Ui message corrections and improvements * "git pull --log" and "git pull --no-log" worked as expected, but "git pull --log=20" did not. * Fix pull.ff configuration overriding merge.ff * fix memory leaks and resource exhaustion errors * documentation fixes * Fix core.excludesfile priorities- git 2.4.2: * "git rev-list --objects $old --not --all" to see if everything that is reachable from $old is already connected to the existing refs was very inefficient. * "hash-object --literally" introduced in v2.2 was not prepared to take a really long object type name. * "git rebase --quiet" was not quite quiet when there is nothing to do. * The completion for "log --decorate=" parameter value was incorrect. * "filter-branch" corrupted commit log message that ends with an incomplete line on platforms with some "sed" implementations that munge such a line. Work it around by avoiding to use "sed". * "git daemon" fails to build from the source under NO_IPV6 configuration (regression in 2.4). * "git stash pop/apply" forgot to make sure that not just the working tree is clean but also the index is clean. The latter is important as a stash application can conflict and the index will be used for conflict resolution. * No longer prepend $GIT_EXEC_PATH and install path to path of executed subprograms and hooks.- git 2.4.1: * git diff bugfixes and improvements * Fix spelling in .gitconfig created upon "git config --global" * "git commit --date=now" or anything that relies on approxidate lost the daylight-saving-time offset. * "git cat-file bl $blob" failed to barf even though there is no object type that is "bl". * Improvements for repositories on NFS- Update to new upstream release 2.4.0 * "git push" has been taught an "--atomic" option that makes a push that updates more than one ref an "all-or-none" affair. * Output from "git log --decorate" now distinguishes between a detached HEAD vs. a HEAD that points at a branch. * The phrasing `git branch` uses to describe a detached HEAD has been updated to agree with the phrasing used by `git status`. * A new "push.followTags" configuration turns the "--follow-tags" option on by default for the `git push` command. - Retrieve tarball signature- git 2.3.7: * An earlier update to the parser that disects a URL broke an address, followed by a colon, followed by an empty string (instead of the port number), e.g. ssh://example.com:/path/to/repo. * The completion script (in contrib/) contaminated global namespace and clobbered on a shell variable $x. * The "git push --signed" protocol extension did not limit what the "nonce" that is a server-chosen string can contain or how long it can be, which was unnecessarily lax. Limit both the length and the alphabet to a reasonably small space that can still have enough entropy.- git 2.3.6: * "diff-highlight" (in contrib/) multibyte character support- git 2.3.5: * The prompt script (in contrib/) did not show the untracked sign when working in a subdirectory without any untracked files. * Even though "git grep --quiet" is run merely to ask for the exit status, we spawned the pager regardless. Stop doing that. * Recommend format-patch and send-email for those who want to submit patches to this project. * An failure early in the "git clone" that started creating the working tree and repository could have resulted in some directories and files left without getting cleaned up. * "git fetch" that fetches a commit using the allow-tip-sha1-in-want extension could have failed to fetch all the requested refs. * The split-index mode introduced at v2.3.0-rc0~41 was broken in the codepath to protect us against a broken reimplementation of Git that writes an invalid index with duplicated index entries, etc. * "git prune" used to largely ignore broken refs when deciding which objects are still being used, which could spread an existing small damage and make it a larger one. * "git tag -h" used to show the "--column" and "--sort" options that are about listing in a wrong section. * The transfer.hiderefs support did not quite work for smart-http transport. * The code that reads from the ctags file in the completion script (in contrib/) did not spell ${param/pattern/string} substitution correctly, which happened to work with bash but not with zsh. * The explanation on "rebase --preserve-merges", "pull - -rebase=preserve", and "push --force-with-lease" in the documentation was unclear.- git 2.3.4: * The 'color.status.unmerged' configuration was not described. * "git log --decorate" did not reset colors correctly around the branch names. * "git -C '' subcmd" refused to work in the current directory, unlike "cd ''" which silently behaves as a no-op. * "git imap-send" learned to optionally talk with an IMAP server via libcURL; because there is no other option when Git is built with NO_OPENSSL option, use that codepath by default under such configuration. * A workaround for certain build of GPG that triggered false breakage in a test has been added. * "git rebase -i" recently started to include the number of commits in the insn sheet to be processed, but on a platform that prepends leading whitespaces to "wc -l" output, the numbers are shown with extra whitespaces that aren't necessary. * We did not parse username followed by literal IPv6 address in SSH transport URLs, e.g. ssh://user@[2001:db8::1]:22/repo.git correctly.- git 2.3.3: * A corrupt input to "git diff -M" used cause us to segfault. * The borrowed code in kwset API did not follow our usual convention to use "unsigned char" to store values that range from 0-255. * Description given by "grep -h" for its --exclude-standard option was phrased poorly. * Documentaton for "git remote add" mentioned "--tags" and "--no-tags" and it was not clear that fetch from the remote in the future will use the default behaviour when neither is given to override it. * "git diff --shortstat --dirstat=changes" showed a dirstat based on lines that was never asked by the end user in addition to the dirstat that the user asked for. * The interaction between "git submodule update" and the submodule.*.update configuration was not clearly documented. * "git apply" was not very careful about reading from, removing, updating and creating paths outside the working tree (under - -index/--cached) or the current directory (when used as a replacement for GNU patch). * "git daemon" looked up the hostname even when "%CH" and "%IP" interpolations are not requested, which was unnecessary. * The "interpolated-path" option of "git daemon" inserted any string client declared on the "host=" capability request without checking. Sanitize and limit %H and %CH to a saner and a valid DNS name.- Fix missing /usr/share/tcsh/git.complete (bnc#919105): git-tcsh-completion-fixes.diff was refreshed for generating the script correctly- git 2.3.2: * "update-index --refresh" used to leak when an entry cannot be refreshed for whatever reason. * "git fast-import" used to crash when it could not close and conclude the resulting packfile cleanly. * "git blame" died, trying to free an uninitialized piece of memory. * "git merge-file" did not work correctly in a subdirectory. * "git submodule add" failed to squash "path/to/././submodule" to "path/to/submodule". * In v2.2.0, we broke "git prune" that runs in a repository that borrows from an alternate object store. * Certain older vintages of cURL give irregular output from "curl-config --vernum", which confused our build system. * Longstanding configuration variable naming rules has been added to the documentation. * Older GnuPG implementations may not correctly import the keyring material we prepare for the tests to use. * Clarify in the documentation that "remote..pushURL" and "remote..URL" are there to name the same repository accessed via different transports, not two separate repositories. * The pack bitmap support did not build with older versions of GCC. * Reading configuration from a blob object, when it ends with a lone CR, use to confuse the configuration parser. * We didn't format an integer that wouldn't fit in "int" but in "uintmax_t" correctly. * "git push --signed" gave an incorrectly worded error message when the other side did not support the capability. * "git fetch" over a remote-helper that cannot respond to "list" command could not fetch from a symbolic reference e.g. HEAD. * The insn sheet "git rebase -i" creates did not fully honor core.abbrev settings. * The tests that wanted to see that file becomes unreadable after running "chmod a-r file", and the tests that wanted to make sure it is not run as root, we used "can we write into the / directory?" as a cheap substitute, but on some platforms that is not a good heuristics. The tests and their prerequisites have been updated to check what they really require. * The configuration variable 'mailinfo.scissors' was hard to discover in the documentation. * Correct a breakage to git-svn around v2.2 era that triggers premature closing of FileHandle. * Even though we officially haven't dropped Perl 5.8 support, the Getopt::Long package that came with it does not support "--no-" prefix to negate a boolean option; manually add support to help people with older Getopt::Long package.- Don't install dummy hg and bzr remote helpers- git 2.3.1: * The interactive "show a list and let the user choose from it" interface "add -i" used showed and prompted to the user even when the candidate list was empty, against which the only "choice" the user could have made was to choose nothing. * "git apply --whitespace=fix" used to under-allocate the memory when the fix resulted in a longer text than the original patch. * "git log --help" used to show rev-list options that are irrelevant to the "log" command. * The error message from "git commit", when a non-existing author name was given as value to the "--author=" parameter, has been reworded to avoid misunderstanding. * A broken pack .idx file in the receiving repository prevented the dumb http transport from fetching a good copy of it from the other side. * The documentation incorrectly said that C(opy) and R(ename) are the only ones that can be followed by the score number in the output in the --raw format. * Fix a misspelled conditional that is always true. * Code to read branch name from various files in .git/ directory would have misbehaved if the code to write them left an empty file. * The "git push" documentation made the "--repo=" option easily misunderstood. * After attempting and failing a password-less authentication (e.g. kerberos), libcURL refuses to fall back to password based Basic authentication without a bit of help/encouragement. * Setting diff.submodule to 'log' made "git format-patch" produce broken patches. * "git rerere" (invoked internally from many mergy operations) did not correctly signal errors when told to update the working tree files and failed to do so for whatever reason. * "git blame HEAD -- missing" failed to correctly say "HEAD" when it tried to say "No such path 'missing' in HEAD".- git 2.3.0: Many small corrections and improvements. - UI, Workflows and Features: * New GIT_SSH_COMMAND environment variable * Can now store empty notes * "git interpret-trailers" learned to properly handle the "Conflicts:" block at the end. * "git am" learned "--message-id" option * "git clone --reference=" learned the "--dissociate" option * "git send-email" learned the "--transfer-encoding" option * "git send-email" learned the "--no-xmailer" option * "git branch -d" (delete) and "git branch -m" (move) learned to honor "-f" (force) flag * "git imap-send" learned to take "-v" (verbose) and "-q" (quiet) command line options.- git 2.2.2: + "git checkout $treeish $path", when $path in the index and the working tree already matched what is in $treeish at the $path, still overwrote the $path unnecessarily. + "git config --get-color" did not parse its command line arguments carefully. + A few code paths used abs() when they should have used labs() on long integers. + "gitweb" used to depend on a behaviour recent CGI.pm deprecated. + "git init" (hence "git clone") initialized the per-repository configuration file .git/config with x-bit by mistake. + Git 2.0 was supposed to make the "simple" mode for the default of "git push", but it didn't. + "Everyday" document had a broken link. + The build procedure did not bother fixing perl and python scripts when NO_PERL and NO_PYTHON build-time configuration changed. + The code that reads the reflog from the newer to the older entries did not handle an entry that crosses a boundary of block it uses to read them correctly. + "git apply" was described in the documentation to take --ignore-date option, which it does not. + Traditionally we tried to avoid interpreting date strings given by the user as future dates, e.g. GIT_COMMITTER_DATE=2014-12-10 when used early November 2014 was taken as "October 12, 2014" because it is likely that a date in the future, December 10, is a mistake. This heuristics has been loosened to allow people to express future dates (most notably, --until= may want to be far in the future) and we no longer tiebreak by future-ness of the date when (1) ISO-like format is used, and (2) the string can make sense interpreted as both y-m-d and y-d-m. Git may still have to use the heuristics to tiebreak between dd/mm/yy and mm/dd/yy, though. + The code to abbreviate an object name to its short unique prefix has been optimized when no abbreviation was requested. + "git add --ignore-errors ..." did not ignore an error to give a file that did not exist. + Git did not correctly read an overlong refname from a packed refs file.- git 2.2.1 Fixes arbitrary command execution vulnerability on case- insensitive file systems. [boo#910756] [CVE-2014-9390] This is not a usual case on GNU/Linux, but this update prevents such commits to propagate to third parties (Windows, OS X) that may be vulnerable.- git 2.2.0: + improvements and updates to UI, Workflows, Features and options + better temporary file handling + API updates + bug fixes - package new git-subtree.html- Add git-credential-gnome-keyring subpackage for GNOME keyring credential storage support- Allow snapshot generation in apparmor profile (bnc#905707)- git 2.1.3: * Some MUAs mangled a line in a message that begins with "From " to ">From " when writing to a mailbox file and feeding such an input to "git am" used to lose such a line. * "git daemon" (with NO_IPV6 build configuration) used to incorrectly use the hostname even when gethostbyname() reported that the given hostname is not found. * Newer versions of 'meld' breaks the auto-detection we use to see if they are new enough to support the `--output` option. * "git pack-objects" forgot to disable the codepath to generate object recheability bitmap when it needs to split the resulting pack. * "gitweb" used deprecated CGI::startfrom, which was removed from CGI.pm as of 4.04; use CGI::start_from instead. * "git log" documentation had an example section marked up not quite correctly, which passed AsciiDoc but failed with AsciiDoctor. * Also contains some documentation updates.- Adapt git-web to newer apache2 (bnc#898318, bnc#897005)- git 2.1.2: * "git push" over HTTP transport had an artificial limit on number of refs that can be pushed imposed by the command line length. * When receiving an invalid pack stream that records the same object twice, multiple threads got confused due to a race. * An attempt to remove the entire tree in the "git fast-import" input stream caused it to misbehave. * Reachability check (used in "git prune" and friends) did not add a detached HEAD as a starting point to traverse objects still in use. * "git config --add section.var val" used to lose existing section.var whose value was an empty string. * "git fsck" failed to report that it found corrupt objects via its exit status in some cases.- git 2.1.1: * Git 2.0 had a regression where "git fetch" into a shallowly cloned repository from a repository with bitmap object index enabled did not work correctly. This has been corrected. * Git 2.0 had a regression which broke (rarely used) "git diff-tree - t". This has been corrected. * "git log --pretty/format=" with an empty format string did not mean the more obvious "No output whatsoever" but "Use default format", which was counterintuitive. Now it means "nothing shown for the log message part". * "git -c section.var command" and "git -c section.var= command" should pass the configuration differently (the former should be a boolean true, the latter should be an empty string), but they didn't work that way. Now it does. * Applying a patch not generated by Git in a subdirectory used to check the whitespace breakage using the attributes for incorrect paths. Also whitespace checks were performed even for paths excluded via "git apply --exclude=" mechanism. * "git bundle create" with date-range specification were meant to exclude tags outside the range, but it did not work correctly. * "git add x" where x that used to be a directory has become a symbolic link to a directory misbehaved. * The prompt script checked $GIT_DIR/ref/stash file to see if there is a stash, which was a no-no. * "git checkout -m" did not switch to another branch while carrying the local changes forward when a path was deleted from the index. * With sufficiently long refnames, fast-import could have overflown an on-stack buffer. * After "pack-refs --prune" packed refs at the top-level, it failed to prune them. * "git gc --auto" triggered from "git fetch --quiet" was not quiet.- git 2.1.0 - incompatible changes: * default pager configuration no longer wraps long lines. To restore: $ git config core.pager "less -S" $ git config pager.blame "less -S" - Changes to specific UI, configuration, workflow and features - Bug fixes and internal improvements - Full list: https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.1.0.txt - remove pathc, upstream: 0001-git-subtree-Use-gitexecdir-instead-of-libexecdir.patch- git 2.0.4: * fix output of "git diff-tree" broken since 2.0.2- git 2.0.3: * An ancient rewrite passed a wrong pointer to a curl library function in a rarely used code path. * "filter-branch" left an empty single-parent commit that results when all parents of a merge commit gets mapped to the same commit, even under "--prune-empty". * "log --show-signature" incorrectly decided the color to paint a mergetag that was and was not correctly validated. * "log --show-signature" did not pay attention to "--graph" option.- git 2.0.2: * Documentation for "git submodule sync" forgot to say that the subcommand can take the "--recursive" option. * Mishandling of patterns in .gitignore that has trailing SPs quoted with backslashes (e.g. ones that end with "\ ") have been corrected. * Recent updates to "git repack" started to duplicate objects that are in packfiles marked with .keep flag into the new packfile by mistake. * "git clone -b brefs/tags/bar" would have mistakenly thought we were following a single tag, even though it was a name of the branch, because it incorrectly used strstr(). * "%G" (nothing after G) is an invalid pretty format specifier, but the parser did not notice it as garbage. * Code to avoid adding the same alternate object store twice was subtly broken for a long time, but nobody seems to have noticed. * A handful of code paths had to read the commit object more than once when showing header fields that are usually not parsed. The internal data structure to keep track of the contents of the commit object has been updated to reduce the need for this double-reading, and to allow the caller find the length of the object. * During "git rebase --merge", a conflicted patch could not be skipped with "--skip" if the next one also conflicted.- git 2.0.1: Maintenance release addressing interaction with tools, usability, performance and misleading behaviour. Full list: https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.0.1.txt- git 2.0.0 - Backward compatibility notes: * git push now uses "simple" semantics by default instead of old "matching", use variable "push.default" to revert * "git add -u" and "git add -A" operate on entire tree, use "git add -u ." or "git add -A ." for current directory only. * "git add " is the same as "git add -A " now, use "git add --ignore-removal " for previous behaviour * "-q" option of "git diff-files" has been removed. To ignore deletion, use "git diff-files --diff-filter=d" * "git request-pull" lost a few "heuristics" * default prefix for "git svn" remote-tracking branches changed from refs/remotes to refs/remotes/origin/ unless with "--prefix" - Updates, fixes and features as listed in: https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.0.0.txt- git 1.9.4: * Commands that take pathspecs on the command line misbehaved when the pathspec is given as an absolute pathname (which is a practice not particularly encouraged) that points at a symbolic link in the working tree. * An earlier fix to the shell prompt script (in contrib/) for using the PROMPT_COMMAND interface did not correctly check if the extra code path needs to trigger, causing the branch name not to appear when 'promptvars' option is disabled in bash or PROMPT_SUBST is unset in zsh. - switch to xz tarball form kernel.org- git 1.9.3: * "git p4" dealing with changes in binary files were broken by a change in 1.9 release. * The shell prompt script (in contrib/), when using the PROMPT_COMMAND interface, used an unsafe construct when showing the branch name in $PS1. * Some more Unicode codepoints defined in Unicode 6.3 as having zero width have been taught to our display column counting logic.- git 1.9.2: * Fix an issue with "git fetch --prune" removing paths on multiple fetch * "git update-ref --stdin" did not fail a request to create a ref when the ref already existed. * "git diff --no-index -Mq a b" fell into an infinite loop. * Do not override GIT_EDITOR when no commit message is required to not affect other uses * "git status --porcelain --branch" showed its output with labels "ahead/behind/gone" translated to the user's locale. * "git mv" that moves a submodule forgot to adjust the array that uses to keep track of which submodules were to be moved to update its configuration * Length limit for the pathname used when removing a path in a deep subdirectory has been removed to avoid buffer overflows. * "git index-pack" used a wrong variable to name the keep-file in an error message when the file cannot be written or closed. * "rebase -i" produced a broken insn sheet when the title of a commit happened to contain '\n' (or ended with '\c') due to a careless use of 'echo'. * Serving objects from a shallow repository needs to write a new file to hold the temporary shallow boundaries but it was not cleaned when we exit due to die() or a signal. * When "git stash pop" stops after failing to apply the stash (e.g. due to conflicting changes), the stash is not dropped. State that explicitly in the output to let the users know. * The labels in "git status" output that describe the nature of conflicts (e.g. "both deleted") were limited to 20 bytes, which was too short for some l10n (e.g. fr). * minor documentation updates- update to 1.9.1 https://raw.github.com/git/git/master/Documentation/RelNotes/1.9.1.txt- update to version 1.9.0 - Rediffed git-zsh-completion-fixes.diff https://raw.github.com/git/git/master/Documentation/RelNotes/1.9.0.txt- Fix a typo in git csh completion (non-existing label); use the normal if/then/endif now instead- Put additional documentation formats (~8 MB) into a separate subpackage- Package the git subtree command - Add 0001-git-subtree-Use-gitexecdir-instead-of-libexecdir.patch - to fix install paths for git-subtree- updated to version 1.8.5.2 https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.5.2.txt- Package also git-remote-hg and git-remote-bzr, so that git clone hg::$URL actually works- Add missing obsoletes for git-remote-helpers subpackage, which was dropped in git 1.8.5- git-tcsh-completion-fixes.diff: git-zsh-completion-fixes.diff: install tcsh and zsh completion files (bnc#853183)- updated to version 1.8.5 * remove git-python-install-fix.diff, no longer to use it. https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.5.txt- updated to version 1.8.4.4 https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.4.4.txt- updated to version 1.8.4.3 https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.4.3.txt- updated to version 1.8.4.2 https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.4.2.txt- updated to version 1.8.4.1 Bug fixes and a handful of trivial code clean-ups, documentation updates, updates to the test suite, etc. https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.4.1.txt- Add dependency on perl-Term-Readkey package to git-svn (bnc#838027)- updated to version 1.8.4: more details, please see here: https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.4.txt- updated to version 1.8.3.4: * The bisect log listed incorrect commits when bisection ends with only skipped ones. * The test coverage framework was left broken for some time. * The test suite for HTTP transport did not run with Apache 2.4. * "git diff" used to fail when core.safecrlf is set and the working tree contents had mixed CRLF/LF line endings. Committing such a content must be prohibited, but "git diff" should help the user to locate and fix such problems without failing.- updated to version 1.8.3.2: * bug fixes and documentation updates more details, please see here: https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.3.2.txt- updated to version 1.8.3.1: * 　bug fixes and documentation updates more details, please see here: https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.3.1.txt- updated to version 1.8.3: * bug fixes and documentation updates more details, please see here: https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.3.txt- updated to version 1.8.2.3: * bug fixes and documentation updates more details, please see here: https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.2.3.txt- revert change from Apr 26 07:22:29 UTC 2013; we will downgrade cvsps package instead of having additional cvsps2, so git-cvs requires cvsps again- Create links from %{gitexecdir}/git instead of %{gitexecdir}/git-add- Updated to version 1.8.2.2: * bug fixes and documentation updates more details, please see here: https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.2.2.txt- Don't own /etc/apache2, buildrequire apache2 instead.- require cvsps2 instead of cvsps [bnc#809800]- updated to version 1.8.2.1: * bug fixes and documentation updates more details, please see here: https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.2.1.txt- Add missing $HOME for git-daemon script that may result in a fatal error at start (bnc#812893)- Enable PCRE and make it possible to use the "grep.patternType=perl" config option- fix git-daemon's pre-uninstall script to correctly stop the daemon after removal (bnc#812123) - fix git-daemon's post-uninstall script to restart the daemon after update (bnc#812123)- updated to version 1.8.2: * a new release of 1.8.x, lots of bug fixes and documentation updates * git-python-install-fix.diff changed more details, please see here: https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.2.txt- updated to version 1.8.1.5: * minor fixes and documentation updates. more details, please see here: https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.1.5.txt- updated to version 1.8.1.4: * "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.- updated to version 1.8.1.3: * minor fixes and documentation updates. more details, please see here: https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.1.3.txt- updated to version 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 . * "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. Also contains various documentation fixes.- updated to version 1.8.1.1: * minor fixes and documentation updates. more details, please see here: https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.1.1.txt- updated to version 1.8.1: * a bit of features. * other minor fixes and documentation updates since v1.8.0. more details, please see here: https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.1.txt.- updated to version 1.8.0.2: * Various codepaths have workaround for a common misconfiguration to spell "UTF-8" as "utf8", but it was not used uniformly. Most notably, mailinfo (which is used by "git am") lacked this support. * We failed to mention a file without any content change but whose permission bit was modified, or (worse yet) a new file without any content in the "git diff --stat" output. * When "--stat-count" hides a diffstat for binary contents, the total number of added and removed lines at the bottom was computed incorrectly. * When "--stat-count" hides a diffstat for unmerged paths, the total number of affected files at the bottom of the "diff --stat" output was computed incorrectly. * "diff --shortstat" miscounted the total number of affected files when there were unmerged paths. * "git p4" used to try expanding malformed "$keyword$" that spans across multiple lines. * "git update-ref -d --deref SYM" to delete a ref through a symbolic ref that points to it did not remove it correctly. * Syntax highlighting in "gitweb" was not quite working. Also contains other minor fixes and documentation updates.- updated to version 1.8.0.1: * a bit of features. * other minor fixes and documentation updates since v1.8.0. more details, please see here: https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.0.1.txt.- updated to version 1.8.0: * a lot of features. * minor documentation updates and code clean-ups. * all the fixes since v1.7.12. more details, please see here: https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.0.txt.- updated to version 1.7.12.4: * "git fetch" over the dumb-http revision walker could segfault when curl's multi interface was used. * It was possible to give specific paths for "asciidoc" and other tools in the documentation toolchain, but not for "xmlto". * "gitweb" did not give the correct committer timezone in its feed output due to a typo. * The "-Xours" (and similarly -Xtheirs) backend option to "git merge -s recursive" was ignored for binary files. Now it is honored. * The "binary" synthetic attribute made "diff" to treat the path as binary, but not "merge". Also contains many documentation updates.- updated to version 1.7.12.3: * "git am" mishandled a patch attached as application/octet-stream (e.g. not text/*); Content-Transfer-Encoding (e.g. base64) was not honored correctly. * It was unclear in the documentation for "git blame" that it is unnecessary for users to use the "--follow" option. * A repository created with "git clone --single" had its fetch refspecs set up just like a clone without "--single", leading the subsequent "git fetch" to slurp all the other branches, defeating the whole point of specifying "only this branch". * "git fetch" over http had an old workaround for an unlikely server misconfiguration; it turns out that this hurts debuggability of the configuration in general, and has been reverted. * "git fetch" over http advertised that it supports "deflate", which is much less common, and did not advertise the more common "gzip" on its Accept-Encoding header. * "git receive-pack" (the counterpart to "git push") did not give progress output while processing objects it received to the puser when run over the smart-http protocol. * "git status" honored the ignore=dirty settings in .gitmodules but "git commit" didn't. Also contains a handful of documentation updates.- Use ./.make also in %check to test exactly what was built - Avoid duplicate file warnings- 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.- updated to version 1.7.12.1: * "git apply -p0" did not parse pathnames on "diff --git" line correctly. This caused patches that had pathnames in no other places to be mistakenly rejected (most notably, binary patch that does not rename nor change mode). Textual patches, renames or mode changes have preimage and postimage pathnames in different places in a form that can be parsed unambiguously and did not suffer from this problem. * "git cherry-pick A C B" used to replay changes in A and then B and then C if these three commits had committer timestamps in that order, which is not what the user who said "A C B" naturally expects. * "git commit --amend" let the user edit the log message and then died when the human-readable committer name was given insufficiently by getpwent(3). * Some capabilities were asked by fetch-pack even when upload-pack did not advertise that they are available. fetch-pack has been fixed not to do so. * "git diff" had a confusion between taking data from a path in the working tree and taking data from an object that happens to have name 0{40} recorded in a tree. * "git for-each-ref" did not correctly support more than one --sort option. * "git log .." errored out saying it is both rev range and a path when there is no disambiguating "--" is on the command line. Update the command line parser to interpret ".." as a path in such a case. * The "--topo-order", "--date-order" (and the lack of either means the default order) options to "rev-list" and "log" family of commands were poorly described in the documentation. * "git prune" without "-v" used to warn about leftover temporary files (which is an indication of an earlier aborted operation). * Pushing to smart HTTP server with recent Git fails without having the username in the URL to force authentication, if the server is configured to allow GET anonymously, while requiring authentication for POST. * The reflog entries left by "git rebase" and "git rebase -i" were inconsistent (the interactive one gave an abbreviated object name). * When "git push" triggered the automatic gc on the receiving end, a message from "git prune" that said it was removing cruft leaked to the standard output, breaking the communication protocol. * "git show --quiet" ought to be a synonym for "git show -s", but wasn't. * "git show --format='%ci'" did not give timestamp correctly for commits created without human readable name on "committer" line. * "git send-email" did not unquote encoded words that appear on the header correctly, and lost "_" from strings. * The interactive prompt "git send-email" gives was error prone. It asked "What e-mail address do you want to use?" with the address it guessed (correctly) the user would want to use in its prompt, tempting the user to say "y". But the response was taken as "No, please use 'y' as the e-mail address instead", which is most certainly not what the user meant. * "gitweb" when used with PATH_INFO failed to notice directories with SP (and other characters that need URL-style quoting) in them. * When the user gives an argument that can be taken as both a revision name and a pathname without disambiguating with "--", we used to give a help message "Use '--' to separate". The message has been clarified to show where that '--' goes on the command line. * When the user exports a non-default IFS without HT, scripts that rely on being able to parse "ls-files -s | while read a b c..." started to fail. Protect them from such a misconfiguration. * The attribute system may be asked for a path that itself or its leading directories no longer exists in the working tree, and it is fine if we cannot open .gitattribute file in such a case. Failure to open per-directory .gitattributes with error status other than ENOENT and ENOTDIR should be diagnosed, but it wasn't. * After "gitk" showed the contents of a tag, neither "Reread references" nor "Reload" did not update what is shown as the contents of it, when the user overwrote the tag with "git tag -f". * "ciabot" script (in contrib/) has been updated with extensive documentation. * "git-jump" script (in contrib/) did not work well when diff.noprefix or diff.mnemonicprefix is in effect. * Older parts of the documentation described as if having a regular file in .git/refs/ hierarchy were the only way to have branches and tags, which is not true for quite some time. * A utility shell function test_seq has been added as a replacement for the 'seq' utility found on some platforms. * Compatibility wrapper to learn the maximum number of file descriptors we can open around sysconf(_SC_OPEN_MAX) and getrlimit(RLIMIT_NO_FILE) has been introduced for portability. * We used curl_easy_strerror() without checking version of cURL, breaking the build for versions before curl 7.12.0. * Code to work around MacOS X UTF-8 gotcha has been cleaned up. * Fallback 'getpass' implementation made unportable use of stdio API. * The "--rebase" option to "git pull" can be abbreviated to "-r", but we didn't document it. * It was generally understood that "--long-option"s to many of our subcommands can be abbreviated to the unique prefix, but it was not easy to find it described for new readers of the documentation set. * The synopsis said "checkout [-B branch]" to make it clear the branch name is a parameter to the option, but the heading for the option description was "-B::", not "-B branch::", making the documentation misleading. Also contains numerous documentation updates.- git-prompt.sh (for __git_ps1) was broken out of git-completion.bash. Install it too.- updated to version 1.7.12: Major version update; new XDG-compliant config file place, new options, new commands: See Documentation/RelNotes/1.7.12.txt for details. - fix broken bash completion when egrep is aliased with --color option (bnc#779536)- updated to version 1.7.11.5: * The Makefile rule to create assembly output (primarily for debugging purposes) did not create it next to the source. * The code to avoid mistaken attempt to add the object directory itself as its own alternate could read beyond end of a string while comparison. * On some architectures, "block-sha1" did not compile correctly when compilers inferred alignment guarantees from our source we did not intend to make. * When talking to a remote running ssh on IPv6 enabled host, whose address is spelled as "[HOST]:PORT", we did not parse the address correctly and failed to connect. * git-blame.el (in compat/) have been updated to use Elisp more correctly. * "git checkout " to come back from a detached HEAD state incorrectly computed reachability of the detached HEAD, resulting in unnecessary warnings. * "git mergetool" did not support --tool-help option to give the list of supported backends, like "git difftool" does. * "git grep" stopped spawning an external "grep" long time ago, but a duplicated test to check internal and external "grep" was left behind.- updated to version 1.7.11: Major version update; added new options in many commands and new push mode like "simple" See Documentation/RelNotes/1.7.11.txt for details. - updated to version 1.7.11.1, 1.7.11.2, 1.7.11.3, 1.7.11.4: Contains many minor fixes, see below for details Documentation/RelNotes/1.7.11.1.txt Documentation/RelNotes/1.7.11.2.txt Documentation/RelNotes/1.7.11.3.txt Documentation/RelNotes/1.7.11.4.txt- updated to version 1.7.10.4: just minor fixes in git-checkout, git-grep, git-rebase, updated translations and documents. See Documentation/RelNotes/1.7.10.4.txt for details.- updated to version 1.7.10.3: * From this release on, the "git merge" command in an interactive session will start an editor when it automatically resolves the merge for the user to explain the resulting commit, just like the "git commit" command does when it wasn't given a commit message. * The "--binary/-b" options to "git am" have been a no-op for quite a while and were deprecated in mid 2008 (v1.6.0). When you give these options to "git am", it will now warn and ask you not to use them. * When you do not tell which branches and tags to push to the "git push" command in any way, the command used "matching refs" rule to update remote branches and tags with branches and tags with the same name you locally have. See details and more changes in Documentation/RelNotes/1.7.10.txt, 1.7.10.1.txt, 1.7.10.2.txt and 1.7.10.3.txt.- Fix build on SLE_11, seems %files there doesn't support more than one -f option- Update to version 1.7.9.2: * Bash completion script (in contrib/) did not like a pattern that begins with a dash to be passed to __git_ps1 helper function. * Adaptation of the bash completion script (in contrib/) for zsh incorrectly listed all subcommands when "git " was given to ask for list of porcelain subcommands. * The build procedure for profile-directed optimized binary was not working very well. * Some systems need to explicitly link -lcharset to get locale_charset(). * t5541 ignored user-supplied port number used for HTTP server testing. * The error message emitted when we see an empty loose object was not phrased correctly. * The code to ask for password did not fall back to the terminal input when GIT_ASKPASS is set but does not work (e.g. lack of X with GUI askpass helper). * We failed to give the true terminal width to any subcommand when they are invoked with the pager, i.e. "git -p cmd". * map_user() was not rewriting its output correctly, which resulted in the user visible symptom that "git blame -e" sometimes showed excess '>' at the end of email addresses. * "git checkout -b" did not allow switching out of an unborn branch. * When you have both .../foo and .../foo.git, "git clone .../foo" did not favor the former but the latter. * "git commit" refused to create a commit when entries added with "add -N" remained in the index, without telling Git what their content in the next commit should be. We should have created the commit without these paths. * "git diff --stat" said "files", "insertions", and "deletions" even when it is showing one "file", one "insertion" or one "deletion". * The output from "git diff --stat" for two paths that have the same amount of changes showed graph bars of different length due to the way we handled rounding errors. * "git grep" did not pay attention to -diff (hence -binary) attribute. * The transport programs (fetch, push, clone)ignored --no-progress and showed progress when sending their output to a terminal. * Sometimes error status detected by a check in an earlier phase of "git receive-pack" (the other end of "git push") was lost by later checks, resulting in false indication of success. * "git rev-list --verify" sometimes skipped verification depending on the phase of the moon, which dates back to 1.7.8.x series. * Search box in "gitweb" did not accept non-ASCII characters correctly. * Search interface of "gitweb" did not show multiple matches in the same file correctly.- updated to v1.7.9: * gitk updates accumulated since early 2011. * git-gui updated to 0.16.0. * git-p4 (in contrib/) updates. * Git uses gettext to translate its most common interface messages into the user's language if translations are available and the locale is appropriately set. Distributors can drop new PO files in po/ to add new translations. * The code to handle username/password for HTTP transactions used in "git push" & "git fetch" learned to talk "credential API" to external programs to cache or store them, to allow integration with platform native keychain mechanisms. * The input prompts in the terminal use our own getpass() replacement when possible. HTTP transactions used to ask for the username without echoing back what was typed, but with this change you will see it as you type. * The internals of "revert/cherry-pick" have been tweaked to prepare building more generic "sequencer" on top of the implementation that drives them. * "git rev-parse FETCH_HEAD" after "git fetch" without specifying what to fetch from the command line will now show the commit that would be merged if the command were "git pull". * "git add" learned to stream large files directly into a packfile instead of writing them into individual loose object files. * "git checkout -B " is a more intuitive way to spell "git reset --keep ". * "git checkout" and "git merge" learned "--no-overwrite-ignore" option to tell Git that untracked and ignored files are not expendable. * "git commit --amend" learned "--no-edit" option to say that the user is amending the tree being recorded, without updating the commit log message. * "git commit" and "git reset" re-learned the optimization to prime the cache-tree information in the index, which makes it faster to write a tree object out after the index entries are updated. * "git commit" detects and rejects an attempt to stuff NUL byte in the commit log message. * "git commit" learned "-S" to GPG-sign the commit; this can be shown with the "--show-signature" option to "git log". * fsck and prune are relatively lengthy operations that still go silent while making the end-user wait. They learned to give progress output like other slow operations. * The set of built-in function-header patterns for various languages knows MATLAB. * "git log --format=''" learned new %g[nNeE] specifiers to show information from the reflog entries when walking the reflog (i.e. with "-g"). * "git pull" can be used to fetch and merge an annotated/signed tag, instead of the tip of a topic branch. The GPG signature from the signed tag is recorded in the resulting merge commit for later auditing. * "git log" learned "--show-signature" option to show the signed tag that was merged that is embedded in the merge commit. It also can show the signature made on the commit with "git commit -S". * "git branch --edit-description" can be used to add descriptive text to explain what a topic branch is about. * "git fmt-merge-msg" learned to take the branch description into account when preparing a merge summary that "git merge" records when merging a local branch. * "git request-pull" has been updated to convey more information useful for integrators to decide if a topic is worth merging and what is pulled is indeed what the requestor asked to pull, including: - the tip of the branch being requested to be merged; - the branch description describing what the topic is about; - the contents of the annotated tag, when requesting to pull a tag. * "git pull" learned to notice 'pull.rebase' configuration variable, which serves as a global fallback for setting 'branch..rebase' configuration variable per branch. * "git tag" learned "--cleanup" option to control how the whitespaces and empty lines in tag message are cleaned up. * "gitweb" learned to show side-by-side diff.- Added the ability to specify the user and group that git-daemon run as (bnc#742661).- Update to v1.7.8.3 * Attempt to fetch from an empty file pretending it to be a bundle did not error out correctly. * gitweb did not correctly fall back to configured $fallback_encoding that is not 'latin1'. * "git clone --depth $n" did not catch a non-number given as $n as an error. * Porcelain commands like "git reset" did not distinguish deletions and type-changes from ordinary modification, and reported them with the same 'M' moniker. They now use 'D' (for deletion) and 'T' (for type-change) to match "git status -s" and "git diff --name-status". * You could make "git commit" segfault by giving the "--no-message" option. * "git checkout -m" did not recreate the conflicted state in a "both sides added, without any common ancestor version" conflict situation. * git native connection going over TCP (not over SSH) did not set SO_KEEPALIVE option which failed to receive link layer errors. * "fast-import" did not correctly update an existing notes tree, possibly corrupting the fan-out. * "git log --follow" did not honor the rename threshold score given with the -M option (e.g. "-M50%"). * Authenticated "git push" over dumb HTTP were broken with a recent change and failed without asking for password when username is given. * "git push" to an empty repository over HTTP were broken with a recent change to the ref handling. * "git push -v" forgot how to be verbose by mistake. It now properly becomes verbose when asked to. * When a "reword" action in "git rebase -i" failed to run "commit --amend", we did not give the control back to the user to resolve the situation, and instead kept the original commit log message. * "git apply --check" did not error out when given an empty input without any patch. * "git archive" mistakenly allowed remote clients to ask for commits that are not at the tip of any ref. * "git checkout" and "git merge" treated in-tree .gitignore and exclude file in $GIT_DIR/info/ directory inconsistently when deciding which untracked files are ignored and expendable. * The function header pattern for files with "diff=cpp" attribute did not consider "type *funcname(type param1,..." as the beginning of a function. * The error message from "git diff" and "git status" when they fail to inspect changes in submodules did not report which submodule they had trouble with. * "git pack-objects" avoids creating cyclic dependencies among deltas when seeing a broken packfile that records the same object in both the deflated form and as a delta.- Implement %check via make test - Update to v1.7.8 New features: * The date parser now accepts timezone designators that lack minutes part and also has a colon between "hh:mm". * The contents of the /etc/mailname file, if exists, is used as the default value of the hostname part of the committer/author e-mail. * "git am" learned how to read from patches generated by Hg. * "git archive" talking with a remote repository can report errors from the remote side in a more informative way. * "git branch" learned an explicit --list option to ask for branches listed, optionally with a glob matching pattern to limit its output. * "git check-attr" learned "--cached" option to look at .gitattributes files from the index, not from the working tree. * Variants of "git cherry-pick" and "git revert" that take multiple commits learned to "--continue" and "--abort". * "git daemon" gives more human readble error messages to clients using ERR packets when appropriate. * Errors at the network layer is logged by "git daemon". * "git diff" learned "--minimal" option to spend extra cycles to come up with a minimal patch output. * "git diff" learned "--function-context" option to show the whole function as context that was affected by a change. * "git difftool" can be told to skip launching the tool for a path by answering 'n' to its prompt. * "git fetch" learned to honor transfer.fsckobjects configuration to validate the objects that were received from the other end, just like "git receive-pack" (the receiving end of "git push") does. * "git fetch" makes sure that the set of objects it received from the other end actually completes the history before updating the refs. "git receive-pack" (the receiving end of "git push") learned to do the same. * "git fetch" learned that fetching/cloning from a regular file on the filesystem is not necessarily a request to unpack a bundle file; the file could be ".git" with "gitdir: " in it. * "git for-each-ref" learned "%(contents:subject)", "%(contents:body)" and "%(contents:signature)". The last one is useful for signed tags. * "git grep" used to incorrectly pay attention to .gitignore files scattered in the directory it was working in even when "--no-index" option was used. It no longer does this. The "--exclude-standard" option needs to be given to explicitly activate the ignore mechanism. * "git grep" learned "--untracked" option, where given patterns are searched in untracked (but not ignored) files as well as tracked files in the working tree, so that matches in new but not yet added files do not get missed. * The recursive merge backend no longer looks for meaningless existing merges in submodules unless in the outermost merge. * "git log" and friends learned "--children" option. * "git ls-remote" learned to respond to "-h"(elp) requests. * "mediawiki" remote helper can interact with (surprise!) MediaWiki with "git fetch" & "git push". * "git merge" learned the "--edit" option to allow users to edit the merge commit log message. * "git rebase -i" can be told to use special purpose editor suitable only for its insn sheet via sequence.editor configuration variable. * "git send-email" learned to respond to "-h"(elp) requests. * "git send-email" allows the value given to sendemail.aliasfile to begin with "~/" to refer to the $HOME directory. * "git send-email" forces use of Authen::SASL::Perl to work around issues between Authen::SASL::Cyrus and AUTH PLAIN/LOGIN. * "git stash" learned "--include-untracked" option to stash away untracked/ignored cruft from the working tree. * "git submodule clone" does not leak an error message to the UI level unnecessarily anymore. * "git submodule update" learned to honor "none" as the value for submodule..update to specify that the named submodule should not be checked out by default. * When populating a new submodule directory with "git submodule init", the $GIT_DIR metainformation directory for submodules is created inside $GIT_DIR/modules// directory of the superproject and referenced via the gitfile mechanism. This is to make it possible to switch between commits in the superproject that has and does not have the submodule in the tree without re-cloning. * "gitweb" leaked unescaped control characters from syntax hiliter outputs. * "gitweb" can be told to give custom string at the end of the HTML HEAD element. * "gitweb" now has its own manual pages. Bugfixes since v1.7.7 * HTTP transport did not use pushurl correctly, and also did not tell what host it is trying to authenticate with when asking for credentials. (merge deba493 jk/http-auth later to maint). * "git blame" was aborted if started from an uncommitted content and the path had the textconv filter in effect. (merge 8518088 ss/blame-textconv-fake-working-tree later to maint). * Adding many refs to the local repository in one go (e.g. "git fetch" that fetches many tags) and looking up a ref by name in a repository with too many refs were unnecessarily slow. (merge 17d68a54d jp/get-ref-dir-unsorted later to maint). * Report from "git commit" on untracked files was confused under core.ignorecase option. (merge 395c7356 jk/name-hash-dirent later to maint). * "git merge" did not understand ":/" as a way to name a commit. " "git push" on the receiving end used to call post-receive and post-update hooks for attempted removal of non-existing refs. (merge 160b81ed ph/push-to-delete-nothing later to maint). * Help text for "git remote set-url" and "git remote set-branches" were misspelled. (merge c49904e fc/remote-seturl-usage-fix later to maint). (merge 656cdf0 jc/remote-setbranches-usage-fix later to maint).- update to git 1.7.7.3: minor bug-fix release; See Documentation/RelNotes/1.7.7.3.txt for details.- update to git 1.7.7.1: - update to git 1.7.7.2: bug-fix releases; See Documentation/RelNotes/1.7.7.1.txt and Documentation/RelNotes/1.7.7.2.txt for details.- license update: GPL-2.0 SPDX format (See http://www.spdx.org/licenses)- correct license tag to "GPL v2 only" (bnc#724499)- split cgit builds to an individual repo- updated to 1.7.7: major update from 1.7.6.x, including i18n/l10n prepartion, updates of git-p4, gitweb, improved coloring, various updates of git-am, git-bisect, git-cherck-attr, etc. See Documentation/RelNotes/1.7.7.txt for details.- updated to 1.7.6.4: minor bug fixes for git-am, git-branch, git-clone, etc See Documentation/RelNotes/1.7.6.4.txt for details.- updated to 1.7.6.2, 1.7.6.3: minor bug fix releases git-fetch performance fix, other fixes in git-reflog, reset, status, tag See Documentation/RelNotes/1.7.6.[23].txt for details.- updated to 1.7.6.1: bug fix release; many fixes for e.g. git checkout, git diff, git fetch, etc. See Documentation/RelNotes/1.7.6.1.txt for details.- Add SuSEfirewall profile for git-daemon (bnc#628048)- update to 1.7.6: major update from 1.7.5.x * Similar to branch names, tagnames that begin with "-" are now disallowed. * Simpler handling of a large file depending on core.bigfilethreshold value * A magic pathspec ":/" handling * Some new options and improvements in git-blame, git-commit, git-diff git-grep, git-format-patch, git-merge, git-svn, etc * More prepartaion for i18n/l10n. See Documentation/RelNotes/1.7.6.txt for details.- fix html path (bnc#675392)- Fix VUL-1: git-web xss (CVE-2011-2186, bnc#698456)- updated to 1.7.5.4: maintainance update, fixing in git-add -p option, git diff -C option, and git-rerere merge error fix, etc- updated to 1.7.5.x: maintenance update release, see Documentation/RelNotes/1.7.5.3.txt Documentation/RelNotes/1.7.5.2.txt Documentation/RelNotes/1.7.5.1.txt - updated to 1.7.5: major version update * Various vcs-svn, git-svn and gitk enhancements and fixes. * Various git-gui updates (0.14.0). * Improved bash completion script * "git repo-config" is officially deprecated * "git checkout" performed on detached HEAD gives a warning * "git cherry-pick" and "git revert" can have a custom merge strategy * "git cherry-pick" remembers which commit failed to apply when it is stopped by conflicts * "git cvsimport" bails out immediately when cvs server is unreachable * "git fetch" vs "git upload-pack" transfer learned 'no-done' protocol extension * "git fetch" can be told to recursively fetch submodules on-demand * "git grep -f " learned to treat "-" * "git init" learned the --separate-git-dir option * "git log" type commands now understand globbing pathspecs * "git log" family of commands learned --cherry and --cherry-mark options * "git mergetool" learned how to drive "beyond compare 3" as well * "git rerere forget" semantic changes * "git push" with no parameters gives better advice messages * a new "git rerere" subcommand "remaining" See more details in Documentation/RelNotes/1.7.5.txt- updated to 1.7.4.2: * documentation updates, small bug fixes; see included Documentation/RelNotes/1.7.4.2.txt- update to 1.7.4.1: * major version update, see included Documentation/RelNotes/1.7.4.txt- mod apache config o remove ending "/" from alias (Alias /git "/usr/share/gitweb/")- updated to git 1.7.3.3: In addition to the usual fixes, this release also includes support for the new "add.ignoreErrors" name given to the existing "add.ignore-errors" configuration variable. - updated to git 1.7.3.4: Among many fixes since v1.7.3.3, it contains a fix to a recently discovered XSS vulnerability in Gitweb (CVE 2010-3906)- fix file list for perl module on factory- update to git 1.7.3.2: This is primarily to push out many documentation fixes accumulated since the 1.7.3.1 release.- updated to git 1.7.3: major version update; new options and behavior for git-rebase, git-clean, git-checkout, git-gui. See release note: http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.7.3.txt - updated to git 1.7.3.1: fix git-stash breakages - Set NO_CROSS_DIRECTORY_HARDLINKS=1 to satisfy BS- updated to git 1.7.2.2: This is primarily for fixing a hanging bug in the smart http transport, but also comes with a lot of documentation udpates. See release note: http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.7.2.2.txt- updated to git 1.7.2.1: minor fixes for git-instaweb, git-web, git-config. See release note: http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.7.2.1.txt- updated to git 1.7.2: mostly bug fixes and small enhancements; see the release note: http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.7.2.txt - gitweb stuff is moved to /usr/share/gitweb- Fix the git.xinetd to be disabled by default and the --base-path setting [bnc#495060, bnc#461726] - Fix missing dependencies of git send-email [bnc#561690] - Fix spurious perl-Error provides [bnc#578273] - Drop global $COMP_WORDBREAKS change from bash-completion [bnc#446506]- install missing gitweb.js- updated to git 1.7.1: including fixes in previous 1.7.0.x releases, a few new behavior changes; see the release note: http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.7.1.txt- require the correct perl-base version- updated to git 1.7.0.4: minor fixes http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.7.0.4.txt- updated to git 1.7.0.3: just minor fixes http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.7.0.3.txt- updated to git 1.7.0.2: http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.7.0.2.txt- updated to git 1.7.0.1; just a minor update http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.7.0.1.txt- don't use %py_requires macro, otherwise it add an implicit dependency to git.rpm- use %_smp_mflags, use %_libexecdir for gitexecdir- fix installation of python stuff- updated to version 1.7.0: Major update See details in http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.7.0.txt Notes on behaviour change: * "git push" into a branch that is currently checked out (i.e. pointed at by HEAD in a repository that is not bare) is refused by default. * "git send-email" does not make deep threads by default when sending a patch series with more than two messages. All messages will be sent as a reply to the first message, i.e. cover letter. * "git status" is not "git commit --dry-run" anymore. This change does not affect you if you run the command without argument. * "git diff" traditionally treated various "ignore whitespace" options only as a way to filter the patch output. "git diff --exit-code -b" exited with non-zero status even if all changes were about changing the amount of whitespace and nothing else; and "git diff -b" showed the "diff --git" header line for such a change without patch text. * External diff and textconv helpers are now executed using the shell. This makes them consistent with other programs executed by git, and allows you to pass command-line parameters to the helpers. Any helper paths containing spaces or other metacharacters now need to be shell-quoted. The affected helpers are GIT_EXTERNAL_DIFF in the environment, and diff.*.command and diff.*.textconv in the config file. * The --max-pack-size argument to 'git repack', 'git pack-objects', and 'git fast-import' was assuming the provided size to be expressed in MiB, unlike the corresponding config variable and other similar options accepting a size value. It is now expecting a size expressed in bytes, with a possible unit suffix of 'k', 'm', or 'g'. - added git-remote-helpers sub-package for python helpers- updated to version 1.6.6: * "git fsck" defaults to "git fsck --full" and will take longer * check "Preparing yourselves for compatibility issues in 1.7.0" section below for the future update http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.6.txt - updated to version 1.6.6.1; minor bug fixes http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.6.1.txt- updated to version 1.6.5.7; minor bug fixes http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.5.6.txt http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.5.7.txt- updated to version 1.6.5.5; only bug fixes; see release notes below; http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.5.4.txt http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.5.5.txt- updated to version 1.6.5.3; see release notes: http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.5.txt http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.5.1.txt http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.5.2.txt http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.5.3.txt- fix build of git-http-push enabling webdav push (bnc#504569)- fix apparmor profile for gitweb- remove git-arch from Recommends of git package; it's totally optional now - remove tla from Requires of git-arch to avoid dependency errors- updated to version 1.6.4.2: * rounding fix for --date=relative output between 1 and 5 years * regression fix of "git add -p" to handleexec bits changes * fix "git apply" to honor GNU diff's convention to mark the creation/deletion event with UNIX epoch timestamp * fix "git checkout" to removed files correctly with symlinks * make "git clean -d -f" safer for separate git repos * fix bugs in "git fetch/push" over http transports * fix "git format-patch --cover-letter" with non-ASCII strings * See details in http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.4.2.txt- updated to version 1.6.4: git push into the currently checked-out branch will be refused by default. See details in http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.4.txt - updated to version 1.6.4.1: Bug fix release. See details in http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.4.1.txt- updated to 1.6.3.3: * fix "git daemon" to correctly parse the initial line * fix "git diff --textconv" memory leak * improved the built-in regular expressions * fix import-tars script (in contrib) to import symbolic links * fix http.c to use correct CURLOPT_SSLKEY * fix low-level filelevel merge driver * fix "git rebase -i" left stray closing parenthesis in reflog * fix "git remote show" to show all the URLs associated with named remotes * fix "whitespace" attribute handling- updated to 1.6.3.1: * fix regression of "git checkout -b new-branch" - updated to 1.6.3.2: * fixes for gcc4.4 builds and others. See below for details http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.3.2.txt- updated to 1.6.3: * major version update: git push behavior change, With the next major release, "git push" into a branch that is currently checked out will be refused by default. You can choose what should happen upon such a push by setting the configuration * Detailed changelog found at http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.3.txt- updated to 1.6.2.4: * The configuration parser had a buffer overflow while parsing an overlong value. * pruning reflog entries that are unreachable from the tip of the ref during "git reflog prune" (hence "git gc") was very inefficient. * "git-add -p" lacked a way to say "q"uit to refuse staging any hunks for the remaining paths. You had to say "d" and then ^C. * "git-checkout " did not update the index entry at the named path; it now does. * "git-fast-export" choked when seeing a tag that does not point at commit. * "git init" segfaulted when given an overlong template location via the --template= option. * "git-ls-tree" and "git-diff-tree" used a pathspec correctly when deciding to descend into a subdirectory but they did not match the individual paths correctly. This caused pathspecs "abc/d ab" to match "abc/0" ("abc/d" made them decide to descend into the directory "abc/", and then "ab" incorrectly matched "abc/0" when it shouldn't). * "git-merge-recursive" was broken when a submodule entry was involved in a criss-cross merge situation.- updated to 1.6.2.2: * A longstanding confusing description of what --pickaxe option of git-diff does has been clarified in the documentation. * "git-blame -S" did not quite work near the commits that were given on the command line correctly. * "git diff --pickaxe-regexp" did not count overlapping matches correctly. * "git diff" did not feed files in work-tree representation to external diff and textconv. * "git-fetch" in a repository that was not cloned from anywhere said it cannot find 'origin', which was hard to understand for new people. * "git-format-patch --numbered-files --stdout" did not have to die of incompatible options; it now simply ignores - -numbered-files as no files are produced anyway. * "git-ls-files --deleted" did not work well with GIT_DIR&GIT_WORK_TREE. * "git-read-tree A B C..." without -m option has been broken for a long time. * git-send-email ignored --in-reply-to when --no-thread was given. * 'git-submodule add' did not tolerate extra slashes and ./ in the path it accepted from the command line; it now is more lenient. * git-svn misbehaved when the project contained a path that began with two dashes. * import-zips script (in contrib) did not compute the common directory prefix correctly. * miscompilation of negated enum constants by old gcc (2.9) affected the codepaths to spawn subprocesses. - updated to 1.6.2.3: * Setting an octal mode value to core.sharedrepository configuration to restrict access to the repository to group members did not work as advertised. * A fairly large and trivial memory leak while rev-list shows list of reachable objects has been identified and plugged. * "git-commit --interactive" did not abort when underlying "git-add -i" signaled a failure. * git-repack (invoked from git-gc) did not work as nicely as it should in a repository that borrows objects from neighbours via alternates mechanism especially when some packs are marked with the ".keep" flag to prevent them from being repacked. - fix the start-check in git-daemon script (bnc#494824)- updated to 1.6.2.1: * .gitignore learned to handle backslash as a quoting mechanism for comment introduction character "#". * timestamp output in --date=relative mode used to display timestamps that are long time ago in the default mode * git-add -i/-p now works with non-ASCII pathnames. * "git hash-object -w" did not read from the configuration file from the correct .git directory. * git-send-email learned to correctly handle multiple Cc: addresses.- updated to 1.6.2: * @{-1} is a way to refer to the last branch you were on. * The location of .mailmap file can be configured * Improvements on "git add -p" * Improvements on "git am" behavior and options * "git blame" aligns author names better * "git clone" now makes its best effort when cloning from an empty repository * "git checkout -" is a shorthand for "git checkout @{-1}". * "git cherry" defaults to whatever the current branch is tracking (if exists) when the argument is not given. * "git cvsserver" fixes / improvements * New options for "git diff" * New options for "git filter-branch" * "git fsck" now checks loose objects in alternate object stores * "git gc --prune" was resurrected to allow "git gc --no-prune" * New option for "git mergetool" * "git rebase -i" can transplant a history down to root * "git reset --merge" option * "git submodule update" learned --no-fetch option. * "git tag" learned --contains For more details, see http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.2.txtlamb21 1539012893 2.13.7-16.12.13.7-16.1gitkgitklibmsgsbg.msgca.msgde.msges.msgfr.msghu.msgit.msgja.msgpt_br.msgpt_pt.msgru.msgsv.msgvi.msggitk.1.gz/usr/bin//usr/share//usr/share/gitk//usr/share/gitk/lib//usr/share/gitk/lib/msgs//usr/share/man/man1/-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -gobs://build.opensuse.org/openSUSE:Maintenance:8885/openSUSE_Leap_42.3_Update/e47f05ac37640c82523f0cb485087597-git.openSUSE_Leap_42.3_Updatedrpmlzma5x86_64-suse-linuxPOSIX shell script, UTF-8 Unicode text executabledirectoryASCII text, with very long linestroff or preprocessor input, ASCII text, with very long lines (gzip compressed data, max compression, from Unix)R^4%.뎺yNApackageand(git-core:tk)?0]"k%H3eg=5^L0+_.BŘyF\w6$lȵ咯"'f30cmT3^ٱI$vP95թ;fJ" 81o=5?34EY=B}~q\5豽kͺpH- `Y<˻Lx_&A۬3T~8Y)%僔i]s඿o,#d5?ۂ'|僾`A&m jN$IZ "ßȟ@}kP;;ł*Μ\gˉs y{mbQY7%!,Zd]N4!q)gQB}񧶱Ur=*Olޑ@).T.';:Ći./34 JvM'GÌ7Js_Ag 7- q5~گoI4#dvn2$uFa5nTxEg֫㴬,kMF(}GQ28F!x}\ NG߆l %>ƽ3w r!l]T]}EasYxIg@]b(Bp!cF2m22T~@Jq6S ][2S0xx~S[8y)_7|wq'S-aY?nFOzB{?4Xf~>=>9 0ᰥR|j99̦@̝J`,uh?G䟽X-?;)w.AUq4D]d$ &j cI3t.Ajï2Aݥ:NfcuW]ڇ]ѶͥeeNK-\zIY)_K6R>Y*!$tFJ^[C** ߢOd@گ9@ ۺ-SfA cEV2%bGO4CzQ=Ux}FbBRV&]UյL>~rRiKkڅ'\#q^G}ŽkMԬdGAF'./W_*&Fs)?<ǰ1Q|cſ=o;if*%M;mf'2x4_zBҏ9Vѵ03<oY]he&Ig~uЬ']*uaBHV{̶O+ EDh{΅W T$_%m [I@!`5T*hӃ& u!(,Q"Z6l7+_}y %@ Y /;"h 1^xqpkq΍$AWɝC1Gb! xayй,C_6@-tXzxMES%f@1WC2DgpNa@UAi ^\D]W+Haъ\CSƙ'Z?dki-qT{2!Td{iQ?C˓] x+Zs=amfQ2.W.2lfϿ`V綍9\]QuD-lXLS-eZ} y91~CEh"ʂ *g@Kns"B1HuDO LGM7 o>g$C(k|V5a&\IO}kn,?j"8e@DӮL} 2҇4A|~fiڠCm/qRxQWU[KWYVY ԃrO䕔'V7)(Q'y[/'^x )a Zg#[7K8>m\]$|=.;Z?F+nަg##%_-guŲK|[>Xh3K; TUL7A"uq-^OX긺p=D1b0r+ 0iQ՛`2OW!NJ6ھgc3f].Ƨ::jҿhE7]Wt%JM6yúU;,$)lw1{,E^&08)yB[Z Cb|B=*C˨>6j ^-TȌ*}A%o?%wcf~hd}W,:ȟxVuZ_g߭Y;OJnErɖ漌lV硘\ ;\呫Q i(1i")E̠0 /7k}6`F[JqB@}+LkjEߣ?E@,{+!K8&A ]0z-8dkЎqZ`w:w "\R̗q4%;bC:߸-4C+k!cQ/4Ԫ\nCJ+kCF ;zMA 9Fv= ?+\0a\\]!KЉ5Sl-"]!ի7.W ާyF)h{HZڝ|W!Z#k1ʄōUx>v]}:kX'S?ZW,) N)B{~n3s)덓-6rfo,$Z n.;hb O[JMp9%ZŇ5nftKKd8*9{fw#5Z[Zٮ* *&<XU7cH^Ƞ8h ekXX[9y.SSKH+1eqWv'BLTr ^¦,-Uǖ MZPs-qXm !?NgɃZ>cT^%ܮYKԦKEtkrQ* ucS<v U12RsQzƲX.K[;;Ed3rTBF w:%NC 8ur!r]UbgD{rڥ.!qEla_$ە#*`bjb`,zUۅWm['*8{c>hc~w`U/KP Cwãlt[@7mɭ+ɛyqW",@bצhN 8.%ǒ3<|]cF=$kH:>C<>ԫ#m.r$nc Rg),*eҵFnMWE//`l>} ev#EF1RNX8˰Uq1pzr+7IB%Dql]4hY>'_P\ȋթЬۈ*>ꝹKjhځ.)A]jf.O7}⤜PΆekHMVUE.f(ZAm2e( l|#3&or_FǼ!Š}4Zriڛ "'pfT?Lb *RED{1a*G^B