Changes between Version 1 and Version 2 of Ticket #29138, comment 19


Ignore:
Timestamp:
10/30/2019 12:41:59 AM (11 months ago)
Author:
Tyler Schwartz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #29138, comment 19

    v1 v2  
    11Joe,
    22
    3 Constantino developed this patch for the project that I succeeded him on, so I'm hardly a random bystander. Everytime our project builds for the past year, it pulls it from this GitHub commit, and I'd love to see that eventually go back to using an official Django release again. I'm not sure how I'd know about 11026, since you didn't link it here. I don't quite know that you mean, because this issue *is* #29138 - perhaps you mean #29010? The patch fixes this issue - can you provide feedback as to what can be done for a fix to be accepted? What specifically *needs improvement*?
     3Constantino developed this patch for the project that I succeeded him on, so I'm hardly a random bystander. Everytime our project builds for the past year, it pulls it from this GitHub commit, and I'd love to see that eventually go back to using an official Django release again. I'm not sure how I'd know about PR 11026, since you didn't reference it here at all. This issue *is* #29138 - perhaps you mean #29010? The patch fixes this issue - can you provide feedback as to what can be done for a fix to be accepted? What specifically *needs improvement*?
    44
    55Thanks,
Back to Top