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

Re: [RFC] push: add documentation on push v2

From
Duy Nguyen <pclouds@gmail.com>
Date
Jul 18, 2018, 18:17 UTC
Message-ID
<CACsJy8Ccjh+Fma_uYPN+_PxUOfAU0nLQVBbVoTLMonhc5ygKcg@mail.gmail.com>
In-Reply-To
<CAGZ79kZ4HOvo-xaDK=USveJ5zaLdJSddh8XNxsOsFHQuu7KcZQ@mail.gmail.com>
On Wed, Jul 18, 2018 at 8:08 PM Stefan Beller <sbeller@google.com> wrote:
Show 8 quoted lines
> P.S.: another feature that just came to mind is localisation of error messages.
> But that is also easy to do with capabilities (the client sends a capability
> such as "preferred-i18n=DE" and the server may translate all its errors
> if it can.
>
> That brings me to another point: do we assume all errors to be read
> by humans? or do we want some markup things in there, too, similar to
> EAGAIN?

We do have several classes of errors (fatal, error, warning) so at least some machine-friendly code should be there. Perhaps just follow many protocols out there (http in particular) and separate error codes in groups. Then we can standardize some specific error codes later if we want too but by default, error(), warning() or die() when running in server context will have a fixed error code in each group.

-- 
Duy
Previous: Stefan BellerNext: Brandon Williams
Message 14 of 19 in “[RFC] push: add documentation on push v2”
  1. Brandon WilliamsJul 17, 2018
  2. Stefan BellerJul 17, 2018
  3. Derrick StoleeJul 18, 2018
  4. Stefan BellerJul 18, 2018
  5. Brandon WilliamsJul 18, 2018
  6. Jeff HostetlerJul 20, 2018
  7. Brandon WilliamsJul 24, 2018
  8. Brandon WilliamsJul 18, 2018
  9. Duy NguyenJul 18, 2018
  10. Brandon WilliamsJul 18, 2018
  11. Duy NguyenJul 18, 2018
  12. Brandon WilliamsJul 18, 2018
  13. Stefan BellerJul 18, 2018
  14. Duy NguyenJul 18, 2018
  15. Brandon WilliamsJul 18, 2018
  16. Brandon WilliamsJul 24, 2018
  17. Duy NguyenJul 25, 2018
  18. Brandon WilliamsJul 25, 2018
  19. Duy NguyenAug 2, 2018

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.