Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

So, suppose you have 2 different contracts. One is extremely favorable to the freelancer, whereas the other one is extremely favorable to the client. And they both have the same git commit id. What does the git commit id help in this situation? What would somebody gain from seeing it?


I think the idea was, if you could codify all your choice parameters, you could end up with a unique identifier for each combination.

Kind of like the six different variants of Creative Commons licenses: CC-BY, CC-BY-SA, CC-BY-NC, CC-BY-NC-SA, CC BY-ND, CC BY-NC-ND.


Okay, that idea makes sense. Though it doesn't sound like the idea described by parent poster, as they were talking about using git commit hashes to identify... something, and obviously the same git commit hash would create all these different combinations.


The git commit hash is yet another dimension, the "version", which is different than the "variant". Like CC-BY-SA-3.0 vs CC-BY-SA-4.0.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: