I Use This!
Activity Not Available

News

Analyzed 4 months ago. based on code collected 4 months ago.
Posted almost 3 years ago by Felipe Contreras
Hi, git-remote-hg is a bidirectional bridge between Git and Mercurial. It is production-ready, has been widely tested, and was previously part of git.git. The big update in v0.6 is support for Python 3 since support for Python 2 has been removed in ... [More] Mercurial 6.2. Other than that there's no difference from v0.5 which includes some minor features, bugfixes, and performance improvements. I've tested as far back as Mercurial 2.4 up to 6.2, all versions work correctly, but Python 3 support seems to work only from around Mercurial 5.3. The testing framework has been updated to test all these versions. https://github.com/felipec/git-remote-hg Cheers. -- Felipe Contreras [Less]
Posted almost 3 years ago by Johannes Schindelin
Dear Git users, I hereby announce that Git for Windows 2.37.2(2) is available from: https://gitforwindows.org/ Changes since Git for Windows v2.37.1 (July 12th 2022) (Upcoming) breaking changes We updated the included Bash to version 5.1 ... [More] (previously 4.4). Please check your shell scripts for potential compatibility issues. Also, as previously announced, Git for Windows dropped support for Windows Vista. Around the beginning of 2023, Git for Windows will drop support for Windows 7 and for Windows 8, following Cygwin's and MSYS2's lead (Git for Windows relies on MSYS2 for components such as Bash and Perl). New Features * Comes with Git v2.37.2. * Comes with tig v2.5.6. * Comes with Bash v5.1 patchlevel 016 . * Comes with Perl v5.36.0. * Git's executables are now marked Terminal Server-aware, meaning: Git will be slightly faster when being run using Remote Desktop Services. * git svn is now based on subversion v1.14.2. * Comes with GNU TLS v3.7.7. Bug Fixes * Git for Windows now ships without the zmore and bzmore utilities (which were broken and included only inadvertently). * A regression in the vimdiff mode of git mergetool has been fixed. * With certain network drives, it was reported that some attributes associated with caching confused Git for Windows. This was fixed. Git-2.37.2.2-64-bit.exe | 6f91f1bb28b222f30c13f905a5e9b0ad491e67c28a37a238000def19f86e0a2f Git-2.37.2.2-32-bit.exe | 672569b7041024b1fdb5c29cc9a775658be78f7d3afea025973e07954f5070fa PortableGit-2.37.2.2-64-bit.7z.exe | 20d9b7e8e8b8b4f27d16420597772e19e7cb1f396b355473867942ed86d0d931 PortableGit-2.37.2.2-32-bit.7z.exe | 36e24698b3cf5270d8276c80a1f7c14ff5d140ee2ac37e8e28a935d0a0ab3418 MinGit-2.37.2.2-64-bit.zip | 12b7c2c8cb9db03fd8c81e618aab196a366d919b2dc0dcd5a062738a07960a05 MinGit-2.37.2.2-32-bit.zip | d3bf1f155872cc431f3ebe898906d6b52988802ff7c3597d9bc16d0937f81209 MinGit-2.37.2.2-busybox-64-bit.zip | 0a299ae5621ef69424d80b27b7a3b177f7299b124139d20afadfed9226648c47 MinGit-2.37.2.2-busybox-32-bit.zip | 69cdd838c924eb4c989652191d77bd9a7ef069e4e059eced69cfeb1e92bfe343 Git-2.37.2.2-64-bit.tar.bz2 | 96b564cfbd99e355e340e1ba5350674fa7c0a04b5390ccca078a1a37637eba6b Git-2.37.2.2-32-bit.tar.bz2 | 153defc4bed02814a772d473ae74a380e68a2377331ee8ad51ac6d21ed35cbbe Ciao, Johannes [Less]
Posted almost 3 years ago by Johannes Schindelin
Dear Git users, I hereby announce that Git for Windows 2.37.2 is available from: https://gitforwindows.org/ Changes since Git for Windows v2.37.1 (July 12th 2022) (Upcoming) breaking changes We updated the included Bash to version 5.1 ... [More] (previously 4.4). Please check your shell scripts for potential compatibility issues. Also, as previously announced, Git for Windows dropped support for Windows Vista. Around the beginning of 2023, Git for Windows will drop support for Windows 7 and for Windows 8, following Cygwin's and MSYS2's lead (Git for Windows relies on MSYS2 for components such as Bash and Perl). New Features * Comes with Git v2.37.2. * Comes with tig v2.5.6. * Comes with Bash v5.1 patchlevel 016 . * Comes with Perl v5.36.0. * Git's executables are now marked Terminal Server-aware, meaning: Git will be slightly faster when being run using Remote Desktop Services. * git svn is now based on subversion v1.14.2. * Comes with GNU TLS v3.7.7. Bug Fixes * Git for Windows now ships without the zmore and bzmore utilities (which were broken and included only inadvertently). * A regression in the vimdiff mode of git mergetool has been fixed. * With certain network drives, it was reported that some attributes associated with caching confused Git for Windows. This was fixed. Git-2.37.2-64-bit.exe | 9020623e95e8f250a6298aa98d4bce395adc121998a65bef143556c3fbd2462c Git-2.37.2-32-bit.exe | 3f1110d855a934194b8de1e032d8edcb622804a0b4223cccb9379f7d37a52915 PortableGit-2.37.2-64-bit.7z.exe | 71294d3008d6da6bd25527498ff726d09d55c2cbd1af32d8e99200d5339d7817 PortableGit-2.37.2-32-bit.7z.exe | 005253af6f96fc86a2ccec97dfd68c56f5b91f72c5cd953e5d1d240c35235390 MinGit-2.37.2-64-bit.zip | 197422464897cfc8f6ebd73007c798658d21310a4c32d43888c9e8f92720ffec MinGit-2.37.2-32-bit.zip | 77b39507cc4b06cad754137e08465c14532b3fc4b0bc4cfc3c91dfeaa6badbe8 MinGit-2.37.2-busybox-64-bit.zip | bfe43199e74d3d80ed7490b7f0aa09a92f907ecbe9ad80719a9bdf6a8ec4ae70 MinGit-2.37.2-busybox-32-bit.zip | a752814318a5cc0c00902d5fafffb97c7201ac2e837e0718eaeaddd3fdf3bb07 Git-2.37.2-64-bit.tar.bz2 | 0508cba06cc52b0e4e733cdd6ee19ad17cc67d31b69c34212f120c94f1806a98 Git-2.37.2-32-bit.tar.bz2 | f2612e4ff5d63d922673b1c6437b8c292ecdcfd950a2f0bdf4704d6eedc42def Ciao, Johannes [Less]
Posted almost 3 years ago by Junio C Hamano
The latest maintenance release Git v2.37.2 is now available at the usual places. This is to merge down the bugfixes accumulated on the 'master' front since Git v2.37.1 was tagged. There was no particular reason why it had to be released today, as ... [More] none of the bugs fixed are security bugs. But there are a few correctness related bugfixes, and users are encouraged to update, unless they are already running 'master' or above, in which case they already have all the fixes that appear here. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/ The following public repositories all have a copy of the 'v2.37.2' tag and the 'maint' branch that the tag points at: url = https://git.kernel.org/pub/scm/git/git url = https://kernel.googlesource.com/pub/scm/git/git url = git://repo.or.cz/alt-git.git url = https://github.com/gitster/git ---------------------------------------------------------------- Git 2.37.2 Release Notes ======================== This primarily is to backport various fixes accumulated on the 'master' front since 2.37.1. Fixes since v2.37.1 ------------------- * "git shortlog -n" relied on the underlying qsort() to be stable, which shouldn't have. Fixed. * Variable quoting fix in the vimdiff driver of "git mergetool". * An earlier attempt to plug leaks placed a clean-up label to jump to at a bogus place, which as been corrected. * Fixes a long-standing corner case bug around directory renames in the merge-ort strategy. * Recent update to vimdiff layout code has been made more robust against different end-user vim settings. * In a non-bare repository, the behavior of Git when the core.worktree configuration variable points at a directory that has a repository as its subdirectory, regressed in Git 2.27 days. * References to commands-to-be-typed-literally in "git rebase" documentation mark-up have been corrected. * Give _() markings to fatal/warning/usage: labels that are shown in front of these messages. * "git mktree --missing" lazily fetched objects that are missing from the local object store, which was totally unnecessary for the purpose of creating the tree object(s) from its input. * Fixes for tests when the source directory has unusual characters in its path, e.g. whitespaces, double-quotes, etc. * Adjust technical/bitmap-format to be formatted by AsciiDoc, and add some missing information to the documentation. * Certain diff options are currently ignored when combined-diff is shown; mark them as incompatible with the feature. * "git clone" from a repository with some ref whose HEAD is unborn did not set the HEAD in the resulting repository correctly, which has been corrected. * mkstemp() emulation on Windows has been improved. * Add missing documentation for "include" and "includeIf" features in "git config" file format, which incidentally teaches the command line completion to include them in its offerings. * Avoid "white/black-list" in documentation and code comments. * Workaround for a compiler warning against use of die() in osx-keychain (in contrib/). * Workaround for a false positive compiler warning. * The resolve-undo information in the index was not protected against GC, which has been corrected. * A corner case bug where lazily fetching objects from a promisor remote resulted in infinite recursion has been corrected. * "git p4" working on UTF-16 files on Windows did not implement CRLF-to-LF conversion correctly, which has been corrected. * "git p4" did not handle non-ASCII client name well, which has been corrected. * "rerere-train" script (in contrib/) used to honor commit.gpgSign while recreating the throw-away merges. * "git checkout" miscounted the paths it updated, which has been corrected. * Fix for a bug that makes write-tree to fail to write out a non-existent index as a tree, introduced in 2.37. * There was a bug in the codepath to upgrade generation information in commit-graph from v1 to v2 format, which has been corrected. Also contains minor documentation updates and code clean-ups. ---------------------------------------------------------------- Changes since v2.37.1 are as follows: Abhradeep Chakraborty (3): bitmap-format.txt: feed the file to asciidoc to generate html bitmap-format.txt: fix some formatting issues bitmap-format.txt: add information for trailing checksum Celeste Liu (1): contrib/rerere-train: avoid useless gpg sign in training Cleber Rosa (1): setup: fix function name in a BUG() message Derrick Stolee (9): t5510: replace 'origin' with URL more carefully vscode: improve tab size and wrapping git-rebase.txt: use back-ticks consistently daemon: clarify directory arguments git-cvsserver: clarify directory list git.txt: remove redundant language t: avoid "whitelist" transport.c: avoid "whitelist" compat/win32: correct for incorrect compiler warning Dimitriy Ryazantcev (1): i18n: mark message helpers prefix for translation Elijah Newren (6): t6429: fix use of non-existent function t6423: add tests of dual directory rename plus add/add conflict merge-ort: small cleanups of check_for_directory_rename merge-ort: make a separate function for freeing struct collisions merge-ort: shuffle the computation and cleanup of potential collisions merge-ort: fix issue with dual rename and add/add conflict Fernando Ramos (1): vimdiff: make layout engine more robust against user vim settings Goss Geppert (2): dir: traverse into repository dir: minor refactoring / clean-up Han Xin (2): commit-graph.c: no lazy fetch in lookup_commit_in_graph() t5330: remove run_with_limited_processses() Jeff King (6): revisions.txt: escape "..." to avoid asciidoc horizontal ellipsis clone: drop extra newline from warning message clone: propagate empty remote HEAD even with other branches clone: use remote branch if it matches default HEAD clone: move unborn head creation to update_head() diff-files: move misplaced cleanup label Johannes Schindelin (3): tests: fix incorrect --write-junit-xml code mergetool(vimdiff): allow paths to contain spaces again shortlog: use a stable sort Junio C Hamano (6): revision: mark blobs needed for resolve-undo as reachable fsck: do not dereference NULL while checking resolve-undo data builtin/remote.c: use the right kind of STRING_LIST_INIT Downmerge a handful of fixes for 2.37.x maintenance track Downmerge a bit more for 2.37.x Git 2.37.2 Kilian Kilger (2): git-p4: fix bug with encoding of p4 client name git-p4: refactoring of p4CmdList() Lessley Dennington (1): osx-keychain: fix compiler warning Li Linchao (1): ls-files: update test style Manuel Boni (1): config.txt: document include, includeIf Martin Ågren (3): config/core.txt: fix minor issues for `core.sparseCheckoutCone` t4200: drop irrelevant code read-cache: make `do_read_index()` always set up `istate->repo` Matheus Tavares (4): checkout: document bug where delayed checkout counts entries twice checkout: show bug about failed entries being included in final report checkout: fix two bugs on the final count of updated entries pkt-line.h: move comment closer to the associated code Moritz Baumann (1): git-p4: fix CR LF handling for utf16 files Philippe Blain (3): diff-format.txt: dst can be 0* SHA-1 when path is deleted, too diff-format.txt: correct misleading wording diff-index.txt: update raw output format in examples René Scharfe (3): combine-diff: abort if --ignore-matching-lines is given combine-diff: abort if --output is given mingw: avoid mktemp() in mkstemp() implementation Richard Oliver (1): mktree: do not check type of remote objects SZEDER Gábor (1): index-format.txt: remove outdated list of supported extensions Tao Klerks (1): rev-parse: documentation adjustment - mention remote tracking with @{u} Taylor Blau (4): pack-objects.h: remove outdated pahole results t5318: demonstrate commit-graph generation v2 corruption commit-graph: introduce `repo_find_commit_pos_in_graph()` commit-graph: fix corrupt upgrade from generation v1 to v2 Ævar Arnfjörð Bjarmason (3): tests: add missing double quotes to included library paths test-lib.sh: fix prepend_var() quoting issue config tests: fix harmless but broken "rm -r" cleanup [Less]
Posted almost 3 years ago by Christian Couder
Hi everyone, The 89th edition of Git Rev News is now published: https://git.github.io/rev_news/2022/07/31/edition-89/ Thanks a lot to Junio Hamano, Philip Oakley and Bruno Brito who helped this month! Enjoy, Christian, Jakub, Markus and ... [More] Kaartic. PS: An issue for the next edition is already opened and contributions are welcome: https://github.com/git/git.github.io/issues/596 [Less]
Posted almost 3 years ago by Taylor Blau
Hi everybody, The Git Merge 2022 speakers, schedule, and ticket registration are all live. The main details are: When: September 14th and 15th Where: Morgan Manufacturing (401 N Morgan), Chicago, Illinois, USA What: Workshops on the 14th ... [More] , main conference on the 15th and the website is up at: https://git-merge.com. The website has links to: - Speaker biographies - (Tentative) schedule for the main conference day - Registration information Like before, if you are interested in coming to the Contributor's Summit, more details are in [1]. I encourage you to read [1] as well as [2], but the most important piece of info is that you should register for the Contributor's Summit separately, and that that ticket is good for both the Contributor's Summit and main conference, so no need to register twice. If you have any questions, please feel free to respond here, or off-list. I am tremendously excited about this event, and I can't wait to see everybody in Chicago soon! Thanks, Taylor [1]: https://lore.kernel.org/git/[email protected]/ [2]: https://lore.kernel.org/git/[email protected]/ [Less]
Posted almost 3 years ago by Taylor Blau
Hi again, Following up on my earlier announcement[1], I have some more details for the Contributor Summit at Git Merge this year: When: September 14th, 12-5pm CDT (UTC-5) Where: Convene (131 S Dearborn) Chicago, Illinois, USA What: ... [More] Contributor's Summit Who: All contributors to Git or related projects in the Git ecosystem are invited; if you're not sure if you qualify, please ask! Registration is now open, though we haven't posted a link to it on the site. If you'd like to register early, you can use the following link below: https://www.eventbrite.com/e/git-merge-2022-tickets-386396170347 If you are planning on attending the Contributor's Summit, please send me an email off-list for a special code to use when registering. This covers both the Contributor's Summit and main registration, so don't register twice :-). As with previous years, you'll have the option of attending for free, or paying the $125 conference fee (all of which goes to Software Freedom Conservancy). Please indicate your preference when emailing me, since there is a separate code for each. If you need financial assistance with covering travel / lodging costs, please reach out to the Git PLC at as soon as possible. A few other pieces of miscellanea: - We're still working out the exact details of an A/V setup for the Contributor's Summit, but the plan is (as in years past) to have some way for folks to be able to join remotely. - We'll have some sort of experts panel at the main conference. The exact format is TBD, but if you are interested in being on that panel, please let me know off-list. - We have a Google Spreadsheet that is being used to collect and vote on topics to discuss at the Contributor's Summit[2]. If you'd like a link to that, please also contact me off-list. The main conference schedule and agenda should be up sometime this week at the usual location below: https://git-merge.com Thanks, Taylor [1]: https://lore.kernel.org/git/[email protected]/ [2]: https://lore.kernel.org/git/[email protected]/ [Less]
Posted almost 3 years ago by Mike Hommey
Hi, Git-cinnabar is a git remote helper to interact with mercurial repositories. It allows to clone, pull and push from/to mercurial remote repositories, using git. Code on https://github.com/glandium/git-cinnabar This release is available on ... [More] https://github.com/glandium/git-cinnabar/releases/tag/0.5.9 What's new since 0.5.8? - Updated git to 2.37.1 for the helper. - Various python 3 fixes. - Fixed stream bundle - Added `python` and `py.exe` as executables tried on top of `python3` and `python2`. - Improved handling of ill-formed local urls. - Fixed using old mercurial libraries that don't support bundlev2 with a server that does. - When fsck reports the metadata as broken, prevent further updates to the repo. - When issue #207 is detected, mark the metadata as broken - Added support for logging redirection to a file - Now ignore refs/cinnabar/replace/ refs, and always use the corresponding metadata instead. - Various `git cinnabar fsck` fixes. Mike [Less]
Posted almost 3 years ago by Johannes Schindelin
Dear Git users, I hereby announce that Git for Windows 2.37.1 is available from: https://gitforwindows.org/ Changes since Git for Windows v2.37.0 (June 27th 2022) This release addresses CVE-2022-31012 and CVE-2022-29187. New Features * ... [More] Comes with Git v2.37.1. * Comes with OpenSSL v1.1.1q. * Comes with Git Credential Manager Core v2.0.785. * Comes with tig v2.5.5. Bug Fixes * Pasting large amounts of text in Git for Windows' Bash when running inside Windows Terminal often resulted in garbled text, which has been fixed. * The Perl module perl-Clone which linked to a non-existing DLL was rebuilt to fix the issue. * The Git for Windows installer can no longer be tricked into running an untrusted git.exe in elevated mode (CVE-2022-31012). * When running Git in a world-writable directory owned by the current user (think C:\Windows\Temp, when running under the SYSTEM account), the checks for dubious ownership of the .git directory now detect this situation properly (CVE-2022-29187). Git-2.37.1-64-bit.exe | 1966761ad2c9e4cbd38f9e583b1125949b011a5a250a99d65e9bb21958e6ef8b Git-2.37.1-32-bit.exe | 714069fe4291c4ca7a51f7e7e81b0c94038590294f3b9e0981456a664c92966b PortableGit-2.37.1-64-bit.7z.exe | b0bc403bb03326b835e239b3bf7c0af277f43eba5421132dc8531204c78b6b25 PortableGit-2.37.1-32-bit.7z.exe | 1a32f1de26d52ef866f27db395d8ab6bd9dc4c53bfc0161937b20f8749b4d96b MinGit-2.37.1-64-bit.zip | edacf2d5c39555c25a396e0b9d27182ab5587259dc2e824b4490996b373f9300 MinGit-2.37.1-32-bit.zip | b336137fb286552c5c2616af50c54e9aca7d16a24ec1b00189a6c221a81af14c MinGit-2.37.1-busybox-64-bit.zip | 1fb7db2cb181ef962e06b1b99c4b254b3ace6f6dce73740bd498d3948189ca42 MinGit-2.37.1-busybox-32-bit.zip | 7470ec55d4ac0ddc3738614dbfe6642770a001b0bae9d3c944e22e25019bf16d Git-2.37.1-64-bit.tar.bz2 | b1c87e136947102ce32f75ef880ebee79b547f8ef33bb1b5010c3455ac83a655 Git-2.37.1-32-bit.tar.bz2 | b0fef8f618e5e5cdad200571211fb6b42be595ef55bf8b648b8211c8bd5e02ea Ciao, Johannes [Less]
Posted almost 3 years ago by Junio C Hamano
Git v2.37.1, together with v2.30.5, v2.31.4, v2.32.3, v2.33.4, v2.34.4, v2.35.4, and v2.36.2 for older maintenance tracks, are now available at the usual places. These are to address CVE-2022-29187, where the fixes in v2.36.1 and below to address ... [More] CVE-2022-24765 released earlier may not have been complete. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/ The following public repositories all have a copy of the 'v2.37.1' tag and other tags for older maintenance tracks. url = https://git.kernel.org/pub/scm/git/git url = https://kernel.googlesource.com/pub/scm/git/git url = git://repo.or.cz/alt-git.git url = https://github.com/gitster/git ---------------------------------------------------------------- Git 2.37.1 Release Notes ======================== This release merges up the fixes that appear in v2.30.5, v2.31.4, v2.32.3, v2.33.4, v2.34.4, v2.35.4, and v2.36.2 to address the security issue CVE-2022-29187; see the release notes for these versions for details. Fixes since Git 2.37 -------------------- * Rewrite of "git add -i" in C that appeared in Git 2.25 didn't correctly record a removed file to the index, which is an old regression but has become widely known because the C version has become the default in the latest release. * Fix for CVE-2022-29187. ---------------------------------------------------------------- Git v2.30.5 Release Notes ========================= This release contains minor fix-ups for the changes that went into Git 2.30.3 and 2.30.4, addressing CVE-2022-29187. * The safety check that verifies a safe ownership of the Git worktree is now extended to also cover the ownership of the Git directory (and the `.git` file, if there is any). Carlo Marcelo Arenas Belón (1): setup: tighten ownership checks post CVE-2022-24765 [Less]