urbit/shrub
1
1
Fork 0
mirror of https://github.com/urbit/shrub.git synced 2024-12-25 13:04:17 +03:00
Code Issues Packages Projects Releases Wiki Activity

Clarify the situations when a new pill is needed

Browse Source
This commit is contained in:
Raymond Pasco 2015-08-29 10:13:04 -04:00
parent 670ef617ed
commit a49ad7a0a7
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
CONTRIBUTING.md
View File

@ -127,10 +127,12 @@ commit.
The requirement here is that every commit that changes the kernel must 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/` 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 for that commit. (Only changing the actual Hoon code counts, so a change
starting up a fakezod actually works as expected. However you do this is to a jet with no corresponding Hoon change does not require a new pill.)
fine, but I like to do it as part of my committing process - just before This is so that checking out an arbitrary revision and starting up a
`git commit`, I fire up a new fakezod. This will use the previous 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 `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` `urb/zod/arvo/`, so `+solid` will compile it. Then I copy `urbit.pill`
into `urb/` and make my commit. into `urb/` and make my commit.