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

Re: [PATCH v7] git-p4: add config git-p4.pathEncoding

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 14, 2015, 18:25 UTC
Message-ID
<xmqqfv2gx3gv.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<1442250640-93838-1-git-send-email-larsxschneider@gmail.com>
larsxschneider@gmail.com writes:
Show 7 quoted lines
> From: Lars Schneider <larsxschneider@gmail.com>
>
> diff to v6:
> * Always print the encoded path in verbose mode.
>
> v6 is already on next (a9e383). This patch must be applied on next.
> Is this the right way to handle this situation?

Yes, I thought that the reviewers found v6 was solid enough, and it is now in 'next'. It is best to do further polishing on the tip of the topic that is in 'next', i.e. a9e38359 (git-p4: add config git-p4.pathEncoding, 2015-09-03).

Labeling the patch as v7 is misleading, but from the context (like your cover letter description) it was clear that the patch is a follow-up, so everything looks good from procedural point of view.

Thanks for making reviewer's life easier.
Previous: Lars Schneider
Message 8 of 8 in “git-p4: add config git-p4.pathEncoding”
  1. git-p4: add config git-p4.pathEncodinglarsxschneider@gmail.com, Sep 14, 2015
  2. git-p4: improve path encoding verbose outputlarsxschneider@gmail.com, Sep 14, 2015
  3. Junio C HamanoSep 14, 2015
  4. Lars SchneiderSep 15, 2015
  5. Luke DiamandSep 15, 2015
  6. Luke DiamandSep 15, 2015
  7. Lars SchneiderSep 15, 2015
  8. Junio C HamanoSep 14, 2015

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.