Re: Samuel: Do you have permission to _enable_ the gccgo patches again?
Svante Signell, on mar. 27 mars 2018 02:52:36 +0200, wrote:
> On Tue, 2018-03-27 at 00:49 +0200, Samuel Thibault wrote:
> > Svante Signell, on lun. 26 mars 2018 19:50:58 +0200, wrote
> > Well, a month is a long time indeed. I guess he needed to move forward,
> > so he dropped; no big deal.
> Yes it is a big deal. If somebody spends numerous (spare time, unpaid) hours
> porting gccgo to Hurd and that work is thrown away then this _is_ a big deal.
What else could he do? Really, please think about it.
No, he does not have (spare, unpaid) time to spend on fixing patches
himself. What option did he have at the time except dropping the
patches? (waiting for fixes is not an option)
> > My point is: no, it's not obvious to just commit and forget. While it
> > *is* obvious to just fix what's currently there. If you don't see why
> > that commit was a move forward concerning Debian, please do check its
> > consequences and think about it.
Please do take a think at what actual benefit my commit had, instead of
assuming that it is necessarily a step back.
> > > As I wrote in that bug report, all needed patches are there. And as the bug
> > > report says: gcc-8 (8-8-20180321-1 and earlier) was successfully built.
> > But that's not the latest version, as you said it, even.
> Latest released Debian version of gcc-8 is 8-8-20180321-1, see
Ok, sorry, above I thought you were referring to thread "Hurd port of
go" which was talking about 8-8-20180312-1,2 only.
Anyway, nobody just applies patch blindly, so no it's not a piece of
cake to apply thousands of lines of patches.