On Mon, Nov 29, 2021 at 8:20 PM Junio C Hamano <gitster@xxxxxxxxx> wrote: > > Han-Wen Nienhuys <hanwen@xxxxxxxxxx> writes: > > > On Fri, Nov 26, 2021 at 9:16 AM Junio C Hamano <gitster@xxxxxxxxx> wrote: > >> > >> The API promises to have only LF, not CRLF, at the end, so > >> strbuf_trim_trailing_newline() is a bit overkill (and if payload > >> happened to end with CR, we would lose it). > > > > it would be best if there was a way to escape characters (ie. "\n" => > > "\\n"). Do we have a function for that? > > Mere escaping would not work in a backward compatible way, without a > trick. It was envisioned that we probably could encode *and* signal I'm talking about the debug output, which isn't subject to compatibility guarantees. -- Han-Wen Nienhuys - Google Munich I work 80%. Don't expect answers from me on Fridays. -- Google Germany GmbH, Erika-Mann-Strasse 33, 80636 Munich Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
