Message ID | 20200912224431.1428-1-luoyonggang@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | W32, W64 msys2/mingw patches | expand |
Patchew URL: https://patchew.org/QEMU/20200912224431.1428-1-luoyonggang@gmail.com/ Hi, This series seems to have some coding style problems. See output below for more information: N/A. Internal error while reading log file The full log is available at http://patchew.org/logs/20200912224431.1428-1-luoyonggang@gmail.com/testing.checkpatch/?type=message. --- Email generated automatically by Patchew [https://patchew.org/]. Please send your feedback to patchew-devel@redhat.com
On 13/09/2020 00.44, Yonggang Luo wrote: > It first introduce msys2 CI on cirrus by fixes nfs, capstone, curses and > disable partial test-char tests. > And then fixes all unit tests failure on msys2/mingw > This fixes the reviews suggested in the mailling list > All cirrus CI are passed Hi, since you're very often sending new versions of your patch series, could you please add a history to the cover letter to say what you changed in each version? Otherwise, your work is very hard to follow. I'd also suggest to really slow down the sending a little bit. Let your patches mature in your tests first, then send out a new series only if you feel that they are really ready. Nobody has the bandwith to review a patch series with 27 patches each day... Thanks, Thomas
On Mon, Sep 14, 2020 at 2:10 PM Thomas Huth <thuth@redhat.com> wrote: > On 13/09/2020 00.44, Yonggang Luo wrote: > > It first introduce msys2 CI on cirrus by fixes nfs, capstone, curses and > > disable partial test-char tests. > > And then fixes all unit tests failure on msys2/mingw > > This fixes the reviews suggested in the mailling list > > All cirrus CI are passed > > Hi, > > since you're very often sending new versions of your patch series, could > you please add a history to the cover letter to say what you changed in > each version? Otherwise, your work is very hard to follow. > I'd also suggest to really slow down the sending a little bit. Let your > patches mature in your tests first, then send out a new series only if > you feel that they are really ready. Nobody has the bandwith to review a > patch series with 27 patches each day... > > Thanks, I am learning how to submit patches properly, in old days, when I am using pull request on github have no such problems. easy to follow up > Thanks, > Thomas > > >
Am 14.09.20 um 08:27 schrieb 罗勇刚(Yonggang Luo): > > Thanks, I am learning how to submit patches properly, in old days, > when I am using pull request on github have no such problems. easy to > follow up May I also ask you to send text-only e-mails? Your HTML e-mails are really hard to read. Thanks, Stefan Weil
On 9/14/20 8:27 AM, 罗勇刚(Yonggang Luo) wrote: > > > On Mon, Sep 14, 2020 at 2:10 PM Thomas Huth <thuth@redhat.com > <mailto:thuth@redhat.com>> wrote: > > On 13/09/2020 00.44, Yonggang Luo wrote: > > It first introduce msys2 CI on cirrus by fixes nfs, capstone, > curses and > > disable partial test-char tests. > > And then fixes all unit tests failure on msys2/mingw > > This fixes the reviews suggested in the mailling list > > All cirrus CI are passed > > Hi, > > since you're very often sending new versions of your patch series, could > you please add a history to the cover letter to say what you changed in > each version? Otherwise, your work is very hard to follow. > I'd also suggest to really slow down the sending a little bit. Let your > patches mature in your tests first, then send out a new series only if > you feel that they are really ready. Nobody has the bandwith to review a > patch series with 27 patches each day... > > Thanks, I am learning how to submit patches properly, in old days, when > I am using pull request on github have no such problems. easy to follow up GitHub pull-request have the same problem, you can update its patches and re-reviewing on top is very difficult. Some old review comments even get deleted. At least having email archive allow us to look back for older versions/comments. Regards, Phil.
On Mon, Sep 14, 2020 at 2:38 PM Stefan Weil <sw@weilnetz.de> wrote: > > Am 14.09.20 um 08:27 schrieb 罗勇刚(Yonggang Luo): > > > Thanks, I am learning how to submit patches properly, in old days, when I am using pull request on github have no such problems. easy to follow up > > > May I also ask you to send text-only e-mails? Your HTML e-mails are really hard to read. > > Thanks, > > Stefan Weil > > Sorry, I am using gmail to send, I'll review the email format in latter messages -- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo
On Sun, Sep 13, 2020 at 7:07 AM <no-reply@patchew.org> wrote: > > Patchew URL: https://patchew.org/QEMU/20200912224431.1428-1-luoyonggang@gmail.com/ > > > > Hi, > > This series seems to have some coding style problems. See output below for > more information: > > N/A. Internal error while reading log file > > > > The full log is available at > http://patchew.org/logs/20200912224431.1428-1-luoyonggang@gmail.com/testing.checkpatch/?type=message . > --- > Email generated automatically by Patchew [https://patchew.org/]. > Please send your feedback to patchew-devel@redhat.com I also have a question about this, This series seems to have some coding style problems, but where to find the logging, seems the logs of patchew are failed(out of disk) -- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo