Commits
- Commit:
466be1387519f6af17726af568d8943cbcf0e66c
- From:
- Mark Jamsek <mark@jamsek.dev>
- Date:
update backout/cherrypick regress for worktree UUID output
ok stsp@
- Commit:
b584caa3e8756aeac18e4d5b3c63cdc8b17ad9ea
- From:
- Mark Jamsek <mark@jamsek.dev>
- Date:
show worktree UUID in backout/cherrypick -l output
When run from the repository, display the UUID to help the user know which
logmsg refs belong to which work tree. Also, use "backout" or "cherrypick"
in the log message header to distinguish output from 'got log'.
Suggested by stsp on irc.
ok stsp@
- Commit:
378a2540886d76e663ffc65125a68c08f8a38604
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
uppercase cherrypick/backout -X progress output
ok jamsek
- Commit:
22d6be814cfc21a663987c0dcb547f99e48a9860
- From:
- Mark Jamsek <mark@jamsek.dev>
- Date:
regress for new backout/cherrypick logmsg references
Tests only cover the -lX interface to list and delete logmsg refs created
by previous backout and cherrypick operations. Further tests are needed
for revert and commit coverage to ensure that the correct log messages of
bo/cy commits are loaded into the editor when 'got commit' is run, and that
only the refs used to populate the editor for the new commit are deleted.
Potential printf issues observed by op remain in the diff; noted here as a
reminder to do a sweep at some point in the future as there are other such
instances in cherrypick.sh and possibly elsewhere in regress.
Reviewed as part of previous commit introducing logmsg ref support for
backed-out/cherrypicked commits.
ok stsp@
- Commit:
b2b3fce13e4eca588bb28a869b07f0063568b505
- From:
- Omar Polo <op@omarpolo.com>
- Date:
respect umask when creating or changing files and directories
This behaviour is already documented in got-worktree(5) but wasn't
actually implemented.
ok stsp@
- Commit:
f1aec6edf3cf139d631d740ffc7f9428c913685c
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
fix regression test failures with Git 3.30.5 / 2.38.1 or later installed
The fix for CVE-2022-39253 in Git made our regression tests fail since
creating submodules from local clones is no longer allowed by default.
Add an override to our invocations of "git submodule add", the same
which was added to Git's regression test suite as part of their fix.
This CVE doesn't otherwise affect us. We do not implement submodules.
Our use of them in regression tests exists only to ensure that Got does not
freak out when it sees one. Precisely because automated support for nested
repositories and/or working copies (as in Git Submodules, or Subversion
Externals, etc.) have been an endless source of security problems in
other systems.
sudden test failures pointed out by naddy@
- Commit:
5e91dae4dd43b8024731223110ab18f505f453ac
- From:
- Josiah Frentsos <jfrent@tilde.team>
- Via:
- Stefan Sperling <stsp@stsp.name>
- Date:
remove trailing whitespace; patch by Josiah Frentsos
- Commit:
8469d82143a591d423c000c47c63bababe6f5716
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
always show commit or tree IDs in diff header, in order to help 'got patch'
The idea is that got patch can simply look for a line such as:
commit - abcde1234567...
to find the merge base commit ID to show in diff3 conflict markers.
got log -p now displays commit IDs in its diff header, instead ofl
tree or blob IDs.
ok op@
- Commit:
842467521f94def2d4cce96b3c39f8bbad73bd0b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
set `ret' in a few places where it was forgotten; ok tracey@
- Commit:
a19f439c4e07de5c812f1771b37cecbba6e631c4
- From:
- Omar Polo <op@omarpolo.com>
- Date:
don't pass $ret to test_done on failure when it's known to be zero
Otherwise the test directory it's not left in place; ok tracey@
- Commit:
49c543a6fe888394ca86e6399c706a9965486134
- From:
- Christian Weisgerber <naddy@mips.inka.de>
- Date:
use test(1) -eq and -ne to compare integers, and reduce quoting
This brings the rest of the regression test scripts in line with
patch.sh.
- Commit:
a8a244dd9f028cb4a3a7f05a51ec1bdcb96f3195
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
simpler fix equivalent to the previous commit
- Commit:
5988bab17145d43dfee07a7a1b779ed17c719420
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
make test_cherrypick_root_commit pass with GOT_TEST_PACK=1
- Commit:
566e0ee7be3658e35381b86aee2469c0838c6985
- From:
- Thomas Adam <thomas@xteddy.org>
- Date:
regress: make test operands POSIX compliant
Since the interpreter for the regress shell scripts are using /bin/sh
this will usually imply some level of POSIX compliance (that isn't
bash-specific, for instance).
Some systems use dash as their sh shell and as such is stricter POSIX
compliance. To help -portable, make the shell test checks use a single
'=' for equality, rather than '=='.
- Commit:
0e039681388d7ec1f832edcbb108ac28db95ae1e
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
preverse binary files during updates and merges
- Commit:
f10244c07ff073c7f69ecf2044ac34e85f0666a0
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
fix merging of files which contain a dot on a line by itself
Annoying bug which we inherited from OpenRCS which inherited
it from OpenBSD's diff3 program.
ok tracey millert
- Commit:
c1e86b1d5bb299f6bcc93a8024575a12da339286
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
add an xfail test for a bug in merging content with a dot on a line by itself
- Commit:
35ca1db76b33010a85a6d0e68e5d78d451028269
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
print additional stats about things that went wrong during a merge
- Commit:
5267b9e4960076d7de62633b9f5f1dcdb6594b33
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
allow bad symlinks to survive a merge
Commands which perform merges will now install bad symlinks as symlinks
in the work tree, instead of creating them as regular files. This means
bad symlinks committed with 'got commit -S' (or Git) will be preserved.
The decision to introduce a bad symlink is done at commit-time and
merges should not forcefully reverse this decision.
The cherrypick and backout commands require a manual commit step, and
a merge result with bad symlinks will require use of 'got commit -S'.
Additional testing by thomas adam
- Commit:
0baddd91502bcd7aca9f72f5ded3609326c953cf
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
add test which covers a cherrypick merge from a branch to itself
- Commit:
ed99f061b0cece8bf32baf31bd5e6b9e39509127
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
add a test case which covers 'got cherrypick' in a mixed-commit work tree
- Commit:
243a13f59c19fd9761211d200b68b77f99f6aded
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
fix bogus error when 'got cherrypick' merges changes into a locally added file
reported by + ok naddy
- Commit:
54d5be07768d1e312078b5eb60f0e32738a1631a
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
fix unrelated changes being merged by got cherrypick/backout/rebase/histedit
This was a long-standing and very annoying bug.
The two xfail tests in the cherrypick test suite are passing now.
- Commit:
3cd22b214454d9973c61426c8a4bd7cf2f8de6ae
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
add an xfail test for a cherrypick bug where unrelated changes get merged
The test case I am using here is a bit large but I could not yet find a way
to make it smaller. If someone knows a smaller test case, please let me know.
naddy caught a small bug in the new test code I had written, thanks!
- Commit:
cce854ad474288cfa4b40b90c875a6b1bb2b67e4
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
add tests for the bug fixed in commit 1fee9f40e2ed335d4ec8899954b59b43990b97c3
one of these tests is still failing; there is another edge case left to fix