On 2/22/12 10:20 PM, Alan M. Carroll wrote:
+1 on "git rebase -i", it's really nice if you want to modify the commit
list, and merge changes, modify messages etc.
Yes, I know about "git rebase -i" but I want something a little more automated
because I will do exactly the same thing every time - squash the local commits and
replace all the commit messages with a bug related one. Why not have a Perl script that
takes the commit message and then handles all the other details?
I'm a bit torn on this for my own commits, I used to squash all commits into
one, but now I think it might many times be better to preserve all, or some
of, those commits. It really depends on the situation I think, but I don't
believe we should be worried about making multiple commits in a change set
for a bug. It's of course up to each individual contributor.
What I would love to see is some way where we can share git branches /
change sets outside of a Jira diff attachment. Sort of what you can do with
github.
-- Leif
