From a49ad7a0a7a6dded5e0ef31de2e3f3e7fd8563e5 Mon Sep 17 00:00:00 2001 From: Raymond Pasco Date: Sat, 29 Aug 2015 10:13:04 -0400 Subject: [PATCH] Clarify the situations when a new pill is needed --- CONTRIBUTING.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ec45927c5..8e8bdd3d2 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -127,10 +127,12 @@ commit. The requirement here is that every commit that changes the kernel must come with an `urbit.pill` built from the same code in `urb/zod/arvo/` -for that commit. This is so that checking out an arbitrary revision and -starting up a fakezod actually works as expected. However you do this is -fine, but I like to do it as part of my committing process - just before -`git commit`, I fire up a new fakezod. This will use the previous +for that commit. (Only changing the actual Hoon code counts, so a change +to a jet with no corresponding Hoon change does not require a new pill.) +This is so that checking out an arbitrary revision and starting up a +fakezod actually works as expected. However you do this is fine, but I +like to do it as part of my committing process - just before `git +commit`, I fire up a new fakezod. This will use the previous `urbit.pill`, but the kernel code in `%clay` will be copied from `urb/zod/arvo/`, so `+solid` will compile it. Then I copy `urbit.pill` into `urb/` and make my commit.