On 2008.09.18 09:13:50 +0300, Boaz Harrosh wrote: > Piet Delaney wrote: > > I think I recall reading that a feature of git was the prevention of the > > git commits > > from being changed. I noticed today that a couple of us have checked in > > files > > without our customary [XTENSA] architecture prefixed to the 1st line of our > > Commit Messages. > > > > I couldn't find a way to do this, other than our reverting back to a > > earlier repository > > and recommitting (each?) change with the slightly changed Commit Message; > > not an attractive investment of our time. > > > > Any suggestions? > > > > -piet > > -- > > git rebase --interactive FIRST_BAD_COMMIT^ will effectively do the same > as above but in a nice automated way. Just change pick => edit on these > patches that need fixing, you'll see. git filter-branch with a suited msg-filter is even more automated :-) Björn -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
