- May 06, 2016
-
-
Greg Wilson authored
-
Greg Wilson authored
-
- May 04, 2016
-
-
Greg Wilson authored
-
- May 02, 2016
-
-
Greg Wilson authored
-
Greg Wilson authored
-
Greg Wilson authored
-
- May 01, 2016
-
-
Greg Wilson authored
-
- Apr 26, 2016
-
-
Greg Wilson authored
-
- Apr 25, 2016
-
-
W. Trevor King authored
The file is not *needed* for anything, because the information is in the Git history. It's just easier to access when it's committed to a file in the repo than it is to ask curious folks to clone the repo and run ‘git shortlog’, etc.
-
W. Trevor King authored
This file was removed in 2e05819f (Naming layouts and inclusions more clearly, 2016-04-19).
-
W. Trevor King authored
-
W. Trevor King authored
-
W. Trevor King authored
GitHub repositories know the repository they were forked from (sort of like the usual 'origin' remote), but I'm not aware of them having other remote-like references. Besides dropping the "other remotes" bit, soften the 'origin' wording. I'm not sure if GitHub uses 'origin' remotes or not to track the parent repository, and the implementation details matter less than the fact that there *is* a reference of some sort to the parent.
-
- Apr 17, 2016
-
-
Greg Wilson authored
-
Greg Wilson authored
-
Greg Wilson authored
-
Greg Wilson authored
-
- Apr 16, 2016
-
-
Greg Wilson authored
-
Greg Wilson authored
-
Greg Wilson authored
-
Greg Wilson authored
-
Greg Wilson authored
-
Greg Wilson authored
-