diff options
author | bt <bt@web> | 2023-12-11 09:55:25 -0500 |
---|---|---|
committer | IkiWiki <ikiwiki.info> | 2023-12-11 09:55:25 -0500 |
commit | 600ada1b01f3cd1e4e20121f58f0ab285f604cd6 (patch) | |
tree | 693f168671dda2e48749d81061d4207a13062b45 /posts | |
parent | 5d0f88cde376d68327909cca3431eea7bbc7b9d9 (diff) |
Diffstat (limited to 'posts')
-rw-r--r-- | posts/git-patches.md | 13 |
1 files changed, 6 insertions, 7 deletions
diff --git a/posts/git-patches.md b/posts/git-patches.md index 2618e6f..78aefb8 100644 --- a/posts/git-patches.md +++ b/posts/git-patches.md @@ -1,6 +1,5 @@ -# Applying Email-Based Git Patches in Evolution on Linux - -2023-04-25 +[[!meta title="Applying Email-Based Git Patches in Evolution on Linux"]] +[[!meta date="2023-04-25"]] Users who work with git patches through email most likely use a terminal-based program such as `aerc` or `mutt`. CLI email clients tend to have built-in support for easily applying patches directly to their local repos. But what about people who prefer to use graphical email apps? @@ -16,12 +15,12 @@ Next, locate the email patch in Evolution and right-click on it. Select "Save as Now simply open your terminal, navigate to your project and run: -``` -git am <path-to-patches-folder>/<patch-filename>.mbox -``` + + git am <path-to-patches-folder>/<patch-filename>.mbox + This should apply the patch directly to your project without issue. You are now free to test these changes locally. If everything looks good, you're able to instantly push these changes remotely. Done and done. -Feel free to purge your `patches` folder regularly or keep them around for future reference if you prefer!
\ No newline at end of file +Feel free to purge your `patches` folder regularly or keep them around for future reference if you prefer! |