On 03/11/10 at 04:33pm, Aaron Griffin wrote:
On Thu, Mar 11, 2010 at 4:29 PM, Daniel J Griffiths (Ghost1227) <ghost1227@archlinux.us> wrote:
On 03/11/10 at 04:26pm, Aaron Griffin wrote:
On Thu, Mar 11, 2010 at 4:13 PM, Daniel J Griffiths (Ghost1227) <ghost1227@archlinux.us> wrote:
On 03/11/10 at 04:06pm, Dan McGee wrote:
On Thu, Mar 11, 2010 at 4:03 PM, Ghost1227 <ghost1227@archlinux.us> wrote:
---
Why do none of your patches have commit messages outside of the subject? Why are these getting removed? What is the new command? How, 6 months from now, am I going to make sense of this commit?
Sorry for sounding like I'm coming down with a hammer on your patches here, but I think this things are truly important.
-Dan Not a problem, the commit messages (with the exception of the first) are taken directly from the commit messages on Aaron's dbscripts branch. The testing2* scripts are being removed because the db-move script can now handle multiple packages in any repo natively.
No they're not. My branch has text there: http://code.phraktured.net/cgit.cgi/dbscripts/log/?h=working
See http://code.phraktured.net/cgit.cgi/dbscripts/commit/?h=working&id=d2a61d7e695b8c956897c42464f39dbbdb39fb5e Oops... sorry about that. Looks like I missed a few notes.
If you added my git repo as a remote and cherry-picked them in, not only would the full commit messages be preserved, but authorship info too Learning experience! Still working on learning how much git can do... --