чување bafe45e64918da8bb09abe5c451ba55a5bfb84a2
родитељ b4beb3b09b48e6310782e0b10160e68af930de4e
Аутор: Страхиња Радић <contact@strahinja.org>
Датум: Sun, 26 May 2024 10:05:48 +0200
HACKING: Add got section
Diffstat:
| M | HACKING | | | 34 | ++++++++++++++++++++++++++++++++-- |
измењених датотека: 1, додавања: 32(+), брисања: 2(-)
diff --git a/HACKING b/HACKING
@@ -21,8 +21,8 @@ files before creating patches to send to me by using the command
issued from the main directory of the repository.
-Creating customizations
------------------------
+Creating customizations (git)
+-----------------------------
It is perhaps the most efficient to create a separate branch with your
modifications in the repository, then:
@@ -47,3 +47,33 @@ instead do:
$ git rebase --rebase-merges master
$ git format-patch master --stdout > my_feature.patch
+
+Creating customizations (got)
+-----------------------------
+
+Note: to my knowing so far, got doesn't support git's email-based workflow; the
+closest thing to git email patches made by git-format-patch(1) is the output of
+`got diff -d`.
+
+With got:
+
+ $ got branch my_feature # if the branch doesn't already exist
+ $ got update -b my_feature # if it does
+
+and after making changes:
+
+ $ got add -R .
+ $ got commit
+ $ got diff -d master my_feature > my_feature.patch
+
+You can then send the file my_feature.patch by email to my public inbox at
+
+ ~strahinja/public-inbox (replace_with_at_sign) lists.sr.ht
+
+To update the branch holding your feature when the upstream changes, you can
+instead do:
+
+ $ got update -b master
+ $ got rebase my_feature
+ $ got diff -d master my_feature > my_feature.patch
+
