On 07/30/2013 10:16 AM, Phil Dibowitz wrote: > On 07/30/2013 08:09 AM, Stephen Warren wrote: >> On 07/30/2013 12:25 AM, Phil Dibowitz wrote: >>> On 07/23/2013 08:15 PM, Scott Talbert wrote: >>>> Use the normal byte ordering for them. Additionally, we were >>>> off by one byte when copying the the serial number data in >>>> UDP_Read(). >>> >>> Applied. >>> >>> Thanks, this format works great. I like this workflow quite a >>> lot. >>> >>> Though I understand why the kernel maintainers are so picky >>> about commit messages now... this flow doesn't give you the >>> opportunity to tweak the message at the last second. >> >> You can edit the saved email, or simply run git commit --amend >> after it's been applied. If you apply a bunch of patches in a >> batch, you can use git rebase -i to edit commit messages further >> back. You likely want to do all that before you push though. > > AFAIK, you can't amend commits by another person, and commit > happens in the tree as you.
No, you can amend any commit without affecting the patch author field. I do it all the time. BTW, I'm pretty sure there's even a cmdline option to "git am" that'll allow you to edit the commit description while the patch is being applied the first time, so there wouldn't even be a need to amend it. ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
