1/29/2024 0 Comments Gitx for linux free![]() I mean, if I were to have a shallow clone of linux around (hint), and that I was forced to unshallow it to use GitX, it would lock up the document for a lonnnng time. My rationale is that I'm not fond of blanket-fetching the repository, because it is shallow for a reason. Time would tell if this becomes a repo of reference on it’s own or not, but if it is maintained throughout the several iterations of OS X updates, over time I believe it would be so.Īfter that point, I'm cautious about the stuff that touches shallow repositories in 97f2e2c. You can see Homebrew as a great example of this model working successfully, where several people can act on incorporating the pull requests into the main repo and making the releases. Direct pull requests would have many who could act on them, reducing the time to get a release out there. A place where could have had an active participation without feeling he is carving yet another corner in the already crowded GitX history.įor example, we would point right at the beginning of the README page to all the relevant existing repos ( etc.) where fixes are drawn from. Bottlenecks on a single person’s schedule can be removed since others can easily take overĬonsider it an aggregator, if you will.Any major changes in direction can be discussed and agreed as a group.People collect and merge patches/fixes waiting in the sidelines of the other repos.I would like to propose we resurface this idea of the organization, not as a blessed repo or with any request for others to discontinue their forks, but rather as a collaborative place where:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |