~jan0sch/darcs-book

Showing details for patch ee5e6a727d469fd439da1c32c13b824368d6f09c.
2018-07-05 (Thu), 8:36 PM - - ee5e6a727d469fd439da1c32c13b824368d6f09c

explain more about patch hashes in chapter 3

Summary of changes
1 files modified with 10 lines added and 3 lines removed
  • en/03-working-locally.md with 10 added and 3 removed lines
diff -rN -u old-darcs-book/en/03-working-locally.md new-darcs-book/en/03-working-locally.md
--- old-darcs-book/en/03-working-locally.md	2024-11-23 23:26:20.972072325 +0000
+++ new-darcs-book/en/03-working-locally.md	2024-11-23 23:26:20.972072325 +0000
@@ -155,14 +155,21 @@
   * add Main.hs
 ```
 
-Here you can see the name we have given to the patch namely 'add Main.hs' as
-well as a hash `2e484ff04a52871b0f2ee643a31c155b24eb1898`. Both can be used to
-identify the patch for later use.
+Here you can see the name we have given to the patch namely 'add Main.hs', the
+author, time and date of its creation and a **hash**
+`2e484ff04a52871b0f2ee643a31c155b24eb1898`. To refer to a specific patch you can
+use its name or the **hash**. The **hash** of a patch is supposed to be unique
+and is generated out of its name, name of its author, time stamp, a random seed,
+as well as some other information (not its content though). It stays the same
+for the entire lifetime of a patch. There are some special operations that allow
+you to fundamentally change a patch and consequently its hash changes as well.
+We will look at these operations in a later chapter.
 
 To get a more detailed output we can issue `darcs log -v` and we can see the
 changes recorded in this patch.
 
 ```
+patch 2e484ff04a52871b0f2ee643a31c155b24eb1898
 Author: raichoo@exmaple.com
 Date:   Tue Jun 26 22:54:24 CEST 2018
   * add Main.hs