git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v4 5/8] status: print per-file porcelain v2 status data

From
Stefan Beller <sbeller@google.com>
Date
Aug 5, 2016, 21:43 UTC
Message-ID
<CAGZ79kb2aO80csCfV=QbH8D1spdNLdkTCSPriZ8W9nSy6T5QAg@mail.gmail.com>
In-Reply-To
<20160805211434.54mtaw2cty4gaxsr@sigill.intra.peff.net>
On Fri, Aug 5, 2016 at 2:14 PM, Jeff King <peff@peff.net> wrote:
Show 6 quoted lines
>
> Unfortunately it is hard for me to test a one-off, as running it locally
> is a complete pain. Stefan set it up long ago to pull "pu" and email out
> the results from their central servers, so I just scan those emails for
> things that look like real issues.
>

I am glad this provides actual value. :) (I tend to ignore the emails nowadays as I am focusing on other stuff. I'll get back to down the number issues eventually, I promise ;)

Running one offs is "relatively" easy. I did that for other projects once upon a time. Here is my script to run the build:

    #!/bin/bash
    . .profile
    cd coverity/git
    git clean -dfx
    git fetch --all
    git checkout origin/pu
    git am ../git_strbuf_stop_out_of_bounds_coverity.patch
    descrip="scripted upload scanning github.com/gitster/git pu"
    name=$(git describe)
    cov-build --dir cov-int make
    tar czvf git-${name}.tgz cov-int
    curl --form project=git \
      --form token=<sekret> \
      --form email=<my mail address> \
      --form file=@git-${name}.tgz \
      --form version="${name}" \
      --form description="${descrip}" \
      https://scan.coverity.com/builds?project=git
    git clean -dfx

You can get a token if you look around, e.g. at https://scan.coverity.com/projects/git/builds/new and the email address is the one you signed up with coverity (or the one from Github, if signed up via Github)

I am currently applying one patch on top of pu, (id: 1434536209-31350-1-git-send-email-pclouds@gmail.com I can resend if you don't have that.)

I am running this script as a cron job, but it can be run "as is" as well, you'd just need to toss in the one-off test patch.

Thanks, Stefan

Previous: Junio C HamanoNext: Stefan Beller
Message 18 of 31 in “status: V2 porcelain status”
  1. 0/8 status: V2 porcelain statusJeff Hostetler, Aug 2, 2016
  2. 2/8 status: cleanup API to wt_status_printJeff Hostetler, Aug 2, 2016
  3. Junio C HamanoAug 3, 2016
  4. Jeff HostetlerAug 4, 2016
  5. 3/8 status: support --porcelain[=<version>]Jeff Hostetler, Aug 2, 2016
  6. Junio C HamanoAug 3, 2016
  7. 8/8 status: tests for --porcelain=v2Jeff Hostetler, Aug 2, 2016
  8. Junio C HamanoAug 5, 2016
  9. Jeff HostetlerAug 5, 2016
  10. 6/8 status: print branch info with --porcelain=v2 --branchJeff Hostetler, Aug 2, 2016
  11. Junio C HamanoAug 5, 2016
  12. Jeff HostetlerAug 5, 2016
  13. 5/8 status: print per-file porcelain v2 status dataJeff Hostetler, Aug 2, 2016
  14. Jeff KingAug 5, 2016
  15. Junio C HamanoAug 5, 2016
  16. Jeff KingAug 5, 2016
  17. Junio C HamanoAug 5, 2016
  18. Stefan BellerAug 5, 2016
  19. Stefan BellerAug 5, 2016
  20. Jeff HostetlerAug 5, 2016
  21. 7/8 git-status.txt: describe --porcelain=v2 formatJeff Hostetler, Aug 2, 2016
  22. Junio C HamanoAug 5, 2016
  23. Jeff HostetlerAug 5, 2016
  24. 1/8 status: rename long-format print routinesJeff Hostetler, Aug 2, 2016
  25. Junio C HamanoAug 3, 2016
  26. Jeff HostetlerAug 4, 2016
  27. 4/8 status: per-file data collection for --porcelain=v2Jeff Hostetler, Aug 2, 2016
  28. Johannes SchindelinAug 3, 2016
  29. Junio C HamanoAug 3, 2016
  30. Johannes SchindelinAug 3, 2016
  31. Junio C HamanoAug 3, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.