diff options
| author | Wolfgang Müller | 2024-09-19 23:13:45 +0200 |
|---|---|---|
| committer | Wolfgang Müller | 2024-09-19 23:13:45 +0200 |
| commit | 3a6d016e9d6a5700d1622d5f9a74a7b21ac885c7 (patch) | |
| tree | 2a347cbbfea67b022f33cfe86a1d576ac6e5d3ed /content | |
| parent | fc7d9c00d65c15a92cbd8e0466ace59bc188e6ea (diff) | |
| download | zunzuncito-3a6d016e9d6a5700d1622d5f9a74a7b21ac885c7.tar.gz | |
Diffstat (limited to 'content')
| -rw-r--r-- | content/8/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/8/index.md b/content/8/index.md index 7bfcbb0..ac4b147 100644 --- a/content/8/index.md +++ b/content/8/index.md @@ -10,7 +10,7 @@ related = [9] +++ When maintaining a project sooner or later there comes the time when you need to -apply patches that have been submitted to you. Assuming a patch-based workflow +apply patches that have been submitted to you. Assuming a patch-based workflow, those are going to be one patch per mail, possibly connected in a thread. There's lots of different ways of getting those patches to their final destination, [`git-am(1)`](https://git-scm.com/docs/git-am), and in this post I |