Skip to content

Commit e4f3692

Browse files
committed
Update original
1 parent e45b334 commit e4f3692

File tree

2 files changed

+9
-9
lines changed

2 files changed

+9
-9
lines changed

doc/develop.jax

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
*develop.txt* For Vim バージョン 9.1. Last change: 2025 Sep 23
1+
*develop.txt* For Vim バージョン 9.1. Last change: 2025 Sep 29
22

33

44
VIMリファレンスマニュアル by Bram Moolenaar

en/develop.txt

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
*develop.txt* For Vim version 9.1. Last change: 2025 Sep 23
1+
*develop.txt* For Vim version 9.1. Last change: 2025 Sep 29
22

33

44
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -388,7 +388,7 @@ unreliable, fails on major platforms (e.g., macOS), and is only part of the
388388
new release workflow. In practice, contributors edit the relevant `.pro` files
389389
by hand when adding, removing, or modifying a function signatures.
390390

391-
This system has been in place since at least v1.24, when Vims functions were
391+
This system has been in place since at least v1.24, when Vim's functions were
392392
still written in K&R style.
393393

394394
==============================================================================
@@ -425,12 +425,12 @@ For any non-trivial change, please always create a pull request on github,
425425
since this triggers the test suite.
426426

427427
A PR should ideally contain a single commit for a single logical change.
428-
However, you can include several commits if you want to group multiple
429-
logical, atomic changes in one PR. This can also make longer PRs easier to
430-
review. Be sure to describe the reasoning for your changes in each commit
431-
message, as this greatly helps with the review process. In cases where each
432-
commit handles different logical changes, they will also be applied as
433-
separate patches in Vims repository.
428+
However, you can include several commits if you want to group multiple logical,
429+
atomic changes in one PR. This can also make longer PRs easier to review. Be
430+
sure to describe the reasoning for your changes in each commit message, as
431+
this greatly helps with the review process. In cases where each commit
432+
handles different logical changes, they will also be applied as separate
433+
patches in Vim's repository.
434434

435435
*style-clang-format*
436436
sound.c and sign.c can be (semi-) automatically formatted using the

0 commit comments

Comments
 (0)