Timeline for How do I manage a major overhaul of an open-source project with git?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 13, 2016 at 21:02 | vote | accept | alexw | ||
| Jun 24, 2016 at 4:43 | comment | added | Winston Ewert | I would suggest that you really want a single configuration file which can override various default settings in the project. | |
| Jun 23, 2016 at 23:31 | comment | added | alexw | Well, most of them won't really need to be changed for a typical installation. So, I guess I could just commit them with their default values. | |
| Jun 23, 2016 at 23:25 | comment | added | Winston Ewert | @alexw, having multiple configuration files is pretty suspect. It sounds like it would make your project difficult to get running because you'd have to setup a whole slew of configuration before it would go. | |
| Jun 23, 2016 at 23:24 | answer | added | Winston Ewert | timeline score: 5 | |
| Jun 23, 2016 at 22:38 | comment | added | alexw | @WinstonEwert just one in the old version, but there will be quite a few in the new version. So, maybe it's not quite as bad as I originally thought. But yes, they will be substantially different in structure. | |
| Jun 23, 2016 at 22:33 | comment | added | Winston Ewert | How many config files do you have? Are they going to be different in the new version? | |
| Jun 23, 2016 at 22:25 | comment | added | alexw | @WinstonEwert config files, mostly. | |
| Jun 23, 2016 at 22:19 | comment | added | Winston Ewert | What are these untracked files? | |
| Jun 23, 2016 at 22:11 | answer | added | usr | timeline score: 2 | |
| Jun 23, 2016 at 21:51 | comment | added | RubberDuck | Why would you have to .gitignore a bunch of files? When you switch branches, they shouldn't remain in your file system. | |
| Jun 23, 2016 at 21:34 | history | edited | alexw | CC BY-SA 3.0 |
added 31 characters in body
|
| Jun 23, 2016 at 21:29 | history | asked | alexw | CC BY-SA 3.0 |