2 ms·
Neat. I'm new to Git, and so far have mostly been treating it like Subversion, emailing patches to each other (yeah... I know... shame on me). Maybe this will h
by tlrobinson 18y ago
Neat. I'm new to Git, and so far have mostly been treating it like Subversion, emailing patches to each other (yeah... I know... shame on me). Maybe this will help transition my way of thinking to "the Git way".
What sort of workflow do you suggest for testing out a set of changes before applying them to your main repository? Perhaps applying them to a test branch or something, then merging the test branch?
edit: just tried this out and got this seemingly impossible status message... "Status: Processing 1 of 0 Commits"
edit2: I didn't actually select any changes to apply... but the status message is deceiving
- schacon 18y agoYes, that would be the suggested workflow - to use this to easily cherry-pick patches into an integration branch that you want and ignore the ones that don't look ready yet. Then pull that one branch down locally and merge it into your master once it's tested. It automatically adds the 'Signed-Off-By' sig and everything. Good catch on the bug, I'll get that fixed.