Is it a common practice to make one commit mixing the changes with origin codes, when forked other's repository? #3980
-
Hi, all, After reading the codes about hashmap, (curiously) I want to know the changes from hashlink to ritelinked only to find one commt alone. So come with this question. Thanks in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
This issue is not related to Databend. As the maintainer of ritelinked, I don't think the behavior of ritelinked is a common practice. The best practice is to maintain the original project, the second best is to fork and keep commits, and the worst is to mix all commits. For the differences between ritelinked and hashlink, and some additional notes, see: PsiACE/ritelinked#6 |
Beta Was this translation helpful? Give feedback.
This issue is not related to Databend.
As the maintainer of ritelinked, I don't think the behavior of ritelinked is a common practice.
The best practice is to maintain the original project, the second best is to fork and keep commits, and the worst is to mix all commits.
For the differences between ritelinked and hashlink, and some additional notes, see: PsiACE/ritelinked#6