+1 from me too On Sat, Jul 18, 2015 at 3:32 AM, Ted Yu <yuzhih...@gmail.com> wrote: > +1 to removing commit messages. > > > >> On Jul 18, 2015, at 1:35 AM, Sean Owen <so...@cloudera.com> wrote: >> >> +1 to removing them. Sometimes there are 50+ commits because people >> have been merging from master into their branch rather than rebasing. >> >>> On Sat, Jul 18, 2015 at 8:48 AM, Reynold Xin <r...@databricks.com> wrote: >>> I took a look at the commit messages in git log -- it looks like the >>> individual commit messages are not that useful to include, but do make the >>> commit messages more verbose. They are usually just a bunch of extremely >>> concise descriptions of "bug fixes", "merges", etc: >>> >>> cb3f12d [xxx] add whitespace >>> 6d874a6 [xxx] support pyspark for yarn-client >>> >>> 89b01f5 [yyy] Update the unit test to add more cases >>> 275d252 [yyy] Address the comments >>> 7cc146d [yyy] Address the comments >>> 2624723 [yyy] Fix rebase conflict >>> 45befaa [yyy] Update the unit test >>> bbc1c9c [yyy] Fix checkpointing doesn't retain driver port issue >>> >>> >>> Anybody against removing those from the merge script so the log looks >>> cleaner? If nobody feels strongly about this, we can just create a JIRA to >>> remove them, and only keep the author names. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org >> For additional commands, e-mail: dev-h...@spark.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org > For additional commands, e-mail: dev-h...@spark.apache.org >
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
