op public repos

Commits

Commit:: f1c9fe20d35f9b64cee89491805039b13c91c8de
From:: Mark Jamsek <mark@jamsek.dev>
Date:: Mon Jan 30 14:58:02 2023 UTC

got: add 'got histedit -d' flag to drop all commits Like -f, except drop all commits. Discussed with op and stsp on irc. ok stsp@

diff | patch | tree

Commit:: 71a61c8ccc19248c397974fbd63b952d2665771c
From:: Stefan Sperling <stsp@stsp.name>
Date:: Sun Jan 29 10:10:04 2023 UTC

use VISUAL instead of EDITOR in histedit_mesg_filemode_change VISUAL is preferred and relying on EDITOR may cause test failures in some environments. pointed out by op and jamsek

diff | patch | tree

Commit:: 9f31ca1f0edf2d4791f35577d55fc5775fff871b
From:: Stefan Sperling <stsp@stsp.name>
Date:: Sun Jan 29 10:08:26 2023 UTC

simplify file content comparison in a regress test; suggested by op@

diff | patch | tree

Commit:: c48f94a406682029fa132ede24321b2622641970
From:: Stefan Sperling <stsp@stsp.name>
Date:: Sun Jan 29 10:06:46 2023 UTC

fix histedit -m on a commit which only changes filemode bits The commit was being miscategorized as a no-op change and dropped. Now the commit is retained and its log message is updated as expected. ok op, jamsek

diff | patch | tree

Commit:: 5f94a4e005d31b60559a66dd5fa48b0ed7348d83
From:: Omar Polo <op@omarpolo.com>
Date:: Fri Nov 18 12:28:43 2022 UTC

regress: consistently use ed -s didn't know about -s when writing those tests; saves some output redirection. ok jamsek

diff | patch | tree

Commit:: b2b3fce13e4eca588bb28a869b07f0063568b505
From:: Omar Polo <op@omarpolo.com>
Date:: Sat Oct 29 18:22:42 2022 UTC

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@

diff | patch | tree

Commit:: 598eac4331d322ab9e91ee6864c54845e3a6e86c
From:: Stefan Sperling <stsp@stsp.name>
Date:: Fri Jul 22 08:26:05 2022 UTC

reset committer during rebase and histedit ok op@

diff | patch | tree

Commit:: 97f28afb9820967508ab57f5ed6a5c75f49464b4
From:: Omar Polo <op@omarpolo.com>
Date:: Wed Jul 20 13:12:45 2022 UTC

regress: add missing return in error path

diff | patch | tree

Commit:: f1e5aff40c5f42ab6fd83a2fb41ca0d10b3b21c9
From:: Omar Polo <op@omarpolo.com>
Date:: Tue Jul 12 17:56:19 2022 UTC

histedit: make sure mesg is only used after pick or edit It doesn't really make sense to use mesg after a fold or drop, or after another mesg. it currently "works" as intended, but the behaviour is confusing and not useful, better abort the operation as it's probably not what the user intended. Suggested by and ok stsp@

diff | patch | tree

Commit:: 49c543a6fe888394ca86e6399c706a9965486134
From:: Christian Weisgerber <naddy@mips.inka.de>
Date:: Thu Mar 31 20:41:38 2022 UTC

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.

diff | patch | tree

Commit:: b4e0802fabd9a36f320a70b8aa668a66533cfb08
From:: Christian Weisgerber <naddy@mips.inka.de>
Date:: Thu Oct 14 18:52:27 2021 UTC

FreeBSD's ed(1) does not accept "0i"; use the equivalent "1i" instead

diff | patch | tree

Commit:: 09209b8a13411e9d8464267c5e65c2c848455496
From:: Stefan Sperling <stsp@stsp.name>
Date:: Fri Oct 8 08:34:39 2021 UTC

add test for merge result when lines are inserted at the top of a file Based on a patch by Omar Polo

diff | patch | tree

Commit:: 41f061b2f459318f3738f59d7676efccc4beb344
From:: Stefan Sperling <stsp@stsp.name>
Date:: Tue Oct 5 14:06:02 2021 UTC

ignore unversioned files while aborting rebase, histedit, merge or operations ok jrick

diff | patch | tree

Commit:: b93c7142c142ac5699accd8dd259187a22e200fb
From:: Stefan Sperling <stsp@stsp.name>
Date:: Fri Oct 1 06:22:27 2021 UTC

add histedit -e option which runs the 'edit' script command for every commit ok jrick

diff | patch | tree

Commit:: ad324bf53a11587dc227a2c00b65020595aa18dc
From:: Stefan Sperling <stsp@stsp.name>
Date:: Tue Sep 21 20:27:45 2021 UTC

fix histedit_no_op test which was failing randomly A no-op replayed history ends up having exactly the same commit IDs if all commits are created at roughly the same moment in time. There are no content changes involved so if commit timestamps do not differ then commit hashes will be the same. In which case there is no fork in history for 'got histedit -l' to display, yet the test was always expecting a fork in history to be displayed. Update the test to take this issue into account. The test will now pass no matter which result is produced by the histedit operation. Problem found by Lucas who observed that this test was randomly failing. Patch also provided by Lucas.

diff | patch | tree

More ↓