Commits
- Commit:
ea4ee74a619549cdfbbf7f824599834f31b72838
- From:
- James Cook <falsifian@falsifian.org>
- Via:
- Omar Polo <op@omarpolo.com>
- Date:
regress/cmdline: fix handling of unexpected success
Diff from James Cook, thanks!
- Commit:
af179be739cacd6576fdf9596ac7e61b714ee367
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
when aborting rebase/histedit/merge, unlink files added by merged changes
Otherwise we leave unversioned files behind in the work tree which may
interfere with new attempts to rebase or merge the changes again.
Problem found by + ok naddy@
- Commit:
5fdcbbb62bc65d9207f8fa4062b856ca904cdcc6
- From:
- Christian Weisgerber <naddy@mips.inka.de>
- Date:
extent regress test to check content after histedit fold operation
- Commit:
9a298e5c10f6c68afbaca853454de2787a312c81
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
support histedit fold operations which delete a file and then add it again
problem found by naddy@
ok op@
- Commit:
15aed0533476711f5f9e6c64c1e220f6e960e7fa
- From:
- Christian Weisgerber <naddy@mips.inka.de>
- Date:
add xfail test for histedit folding of delete followed by add
If a file is deleted, then in modified form added again, folding
should restore the file with its new contents.
ok stsp
- Commit:
885e96dfba200f362ddd1d9795740251bcb6e39b
- From:
- Christian Weisgerber <naddy@mips.inka.de>
- Date:
regress: replace "sed -i" with ed(1) for portable in-place editing
"sed -i" is fundamentally unportable. GNU and OpenBSD sed(1) treat
the extension for the backup file as an optional argument and use
"sed -i" for no backup file. FreeBSD sed(1) treats the extension
as an obligatory argument and uses "sed -i ''" for no backup file.
There is no single syntax that works for both.
ok stsp op
- Commit:
f1c9fe20d35f9b64cee89491805039b13c91c8de
- From:
- Mark Jamsek <mark@jamsek.dev>
- Date:
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@
- Commit:
71a61c8ccc19248c397974fbd63b952d2665771c
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
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
- Commit:
9f31ca1f0edf2d4791f35577d55fc5775fff871b
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
simplify file content comparison in a regress test; suggested by op@
- Commit:
c48f94a406682029fa132ede24321b2622641970
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
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
- Commit:
5f94a4e005d31b60559a66dd5fa48b0ed7348d83
- From:
- Omar Polo <op@omarpolo.com>
- Date:
regress: consistently use ed -s
didn't know about -s when writing those tests; saves some output
redirection.
ok jamsek
- 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:
598eac4331d322ab9e91ee6864c54845e3a6e86c
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
reset committer during rebase and histedit
ok op@
- Commit:
97f28afb9820967508ab57f5ed6a5c75f49464b4
- From:
- Omar Polo <op@omarpolo.com>
- Date:
regress: add missing return in error path
- Commit:
f1e5aff40c5f42ab6fd83a2fb41ca0d10b3b21c9
- From:
- Omar Polo <op@omarpolo.com>
- Date:
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@