> -------------------------------------------------- > [Stalled] > > * kk/maint-prefix-in-config-mak (2011-05-04) 3 commits > - config.mak.in: allow "configure --sysconfdir=/else/where" > - Makefile: allow sysconfdir to be used from configure > (merged to 'next' on 2011-05-02 at c747ba3) > + Honor $(prefix) set in config.mak* when defining ETC_GIT* and sysconfdir > > J6t is unhappy that sysconfdir is ignored in relocatable case. Although I > personally do not think that is a problem, as it has never been an issue, > let's see what others think. > > * jn/gitweb-js (2011-04-28) 13 commits > - gitweb: Make JavaScript ability to adjust timezones configurable > - gitweb.js: Add UI for selecting common timezone to display dates > - gitweb: JavaScript ability to adjust time based on timezone > - gitweb: Unify the way long timestamp is displayed > - gitweb: Refactor generating of long dates into format_timestamp_html > - gitweb.js: Provide getElementsByClassName method (if it not exists) > - gitweb.js: Introduce code to handle cookies from JavaScript > - gitweb.js: Extract and improve datetime handling > - gitweb.js: Provide default values for padding in padLeftStr and padLeft > - gitweb.js: Update and improve comments in JavaScript files > - gitweb: Split JavaScript for maintability, combining on build > - Remove gitweb/gitweb.cgi and other legacy targets from main Makefile > - git-instaweb: Simplify build dependency on gitweb > Sorry if this is dumb, as I'm unsure how Git (the mailing list) handles regression tracking, but I saw no mention of this thread: http://marc.info/?l=git&m=130445013906259&w=2 Is this something overlooked or something you're aware of just not worried about at the minute. What is the process if a merge to master causes a regression, do you just git revert the offending merge, fix on the branch, then re-merge? Many thanks - cj. -- 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