Petr Baudis <pasky@xxxxxx> writes: > Hi, > > participating in this might be fun, even if there is not much time > left to sign up: > > http://www.hackontest.org/index.php?action=Root-projectDetail(120) > > (What feature in Git or a Git-related tool would you implement, given 24 > hours staight and unlimited pizza supply?) A few ideas (some might be repeated) * resumable clone * git-push implemented as CGI * support for ftp, ftps, sftp fetch * support for gits (git over SSL/TLS) fetch * relative blame, i.e. if you have blame data for some revision (for example in "git gui blame") you want to have data for some revision which is either direct ancestor or direct descendant of the revision you have blame data for, aka "git blame --relative" * "tree" blame, i.e. something like VievVC or GitHub shows: for exach entry in a tree commit which brought it to current version * graph log for gitweb, either generating images on the fly, or using a few pre-defined images ('|', '-', '\', '/', etc.) and CSS. * "MediaWiki history"-like or "MoinMoin info"-like view for gitweb * improvements to "git log --follow" so it works also for nonlinear history (for example "git log --follow gitweb/gitweb.perl" following to the very first version of gitweb, then as gitweb.cgi) * graphical history viewer for Git mode in Emacs. * context sensitive searching in gitweb, for example searching commits on given branch, or grepping files in given directory * handling of svn:externals using submodules * custom merge strategy for ChangeLog, for .po files Blame merge strategy would take probably much more that 24h solely in the initial design phase... -- Jakub Narebski Poland ShadeHawk on #git -- 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
