Re: [PATCH 1/4] config --show-origin: report paths with forward slashes

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Apr 4, 2016, 20:42 UTC
Message-ID: <alpine.DEB.2.20.1604042242110.3371@virtualbox>
In-Reply-To: <xmqqd1q574p8.fsf@gitster.mtv.corp.google.com>

Hi Junio,

On Mon, 4 Apr 2016, Junio C Hamano wrote:

Show 15 quoted lines

> Johannes Sixt <j6t@kdbg.org> writes:
> 
> > Although I am convinced that the change is not necessary for
> > correctness, I can buy the justification that we should produce forward
> > slashes for consistency. There are a number of occasions where we
> > present paths to the user, and we do show forward-slashes in all cases
> > that I found. We should keep the commit.
> >
> > But then let's do this:
> 
> Sounds like a plan; even though I am mildly against adding more
> platform specific #ifdef to files outside compat/, this patch does
> not.
> 
> Dscho?

Fine by me! Dscho

$ 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.