Re: A plea for volunteers (Fwd: CVS support at SourceForge ends Nov. 30)

[Allin C. <cot...@wf...>]

On Sun, 8 Oct 2017, Daniel J Sebald wrote:

> On 10/07/2017 02:32 PM, Daniel J Sebald wrote:
>> On 10/07/2017 01:30 PM, sfeam via gnuplot-beta wrote:
> [snip]
>> Another question is SourceForge's support for an HTML interface to the git 
>> repository.  It's nice to have an HTML-viewable log of what's going on 
>> rather than have to pull all the latest changesets.  Do maintainers want to 
>> go all out with pull-requests, etc.?  Probably not, seeing as changes are 
>> sort of funneled down to a few people for review, rather than having a 
>> whole large team of players committing to the canonical repository.  So, in 
>> that respect, SourceForge's support for pull-requests isn't that critical. 
>> Just a nice log and difference viewer is good.  Staying with SourceForge is 
>> fine with me, if that criteria can be met.
>
> Here are a couple examples of HTML interface to repositories on SourceForge; 
> one SVN, one git:
>
> SVN
> https://sourceforge.net/p/skychart/code/3668/log/
>
> git
> https://sourceforge.net/p/maxima/website/commit_browser
>
> Neither are the most elegant such interface I've seen, but the basic elements 
> are there, i.e., a list of changes and a means to get the diff hunks for that 
> change.  SVN HTML actually looks a little better in the sense that it allows 
> viewing diff hunks for all changed files at once [...]

You get that in the HTML git viewer if you click on the commit ID -- 
if I'm understanding you right. (You see diff hunks for all files 
affecting by the given commit.)

Allin