I'm newbie in git and I'm trying to use it as follows (AFAIK it's a quite common workflow for a single developer):
Now I'm about migrating some of my projects (related to a single workspace, ie working tree) to a new version of compiler. On a feature branch msvc90 I prepared a lot of work to be committed. I have two options know:
My question is quite philosophical. The second option seems to be slightly preferable for me as it keeps more details in history. On the other hand I have read some git tutorials that recommend to keep well-consistent commits only (eg to use bisect).
Does anyone know examples of big projects whose policy permits keeping inconsistent commits of this kind (on feature branches)?
If in doubt, keep the commits small. Bisect allows you to have "don't know" answer instead of just "yes" or "no". More information is always better as you can reduce later if need be. You can't do it the other way around.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.