Thread (1 message) 1 message, 1 author, 2016-08-11
  • (off-list ancestor, not in this archive)
  • Re: What's in git.git · Junio C Hamano <hidden> · 2016-08-11

Re: What's in git.git

From: Junio C Hamano <hidden>
Date: 2016-08-11 20:01:35

Jakub Narebski [off-list ref] writes:
Junio C Hamano wrote:
quoted
   Jakub Narebski (4):
[...]
quoted
      gitweb: Output also empty patches in "commitdiff" view
I think that this patch is a bit premature. Without "new improved patchset
view" the empty patches are just that: totally empty. It is new header and
especially outputting extended header information which makes outputting
"empty" patches (with no diff) in "commitdiff" view usefull. By "empty"
patches I mean pure type change, pure rename, pure copy and type change and
rename.

The "new improved patchset view" is prepared to send in two stages...
At least this does not break the page even without these two
follow-ups.  If the follow-ups come in time and do not break the
page, they are very welcome post -rc1 fixes to have before the
final release.  On the other hand, even if they don't, it's not
the end of the world ;-).
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help