Re:Molly for Android: A fork of Signal for Android with pass...
by lsaferite on Tuesday January 12, 2021 @09:26AM
(#25747275)
Sounds like they don't use github to manage the codebase.
[ Parent
| on HN ]
Re:Molly for Android: A fork of Signal for Android with pass...
by jwieczorek on Tuesday January 12, 2021 @09:42AM
(#25747483)
But Git is a distributed VCS. They could just as well cleanly merge pull requests into the main branch as hosted on GitHub and then merge GitHub's main branch into their canonical system's main branch.
Re:Molly for Android: A fork of Signal for Android with pass...
by lsaferite on Tuesday January 12, 2021 @09:59AM
(#25747715)
I just randomly picked a contribution from an external party. The commit that made it into mainline has an author set to the person that contributed the code originally and a committer set to one of the 'signal.org' members. I'm confused why people would have a problem with how they chose to manage their code if the original attribution is not lost in the process. I'm fairly certain the Linux codebase is managed similarly.
Edit: adding links I forgot https://github.com/signalapp/Signal-Android/pull/10219 https://github.com/signalapp/Signal-Android/commit/dda51bf36...
Re:Molly for Android: A fork of Signal for Android with pass...
by eat_veggies on Tuesday January 12, 2021 @09:47AM
(#25747561)
Git is a distributed VCS, so if another tool works better for their workflow, then they can use that instead of GitHub