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

Re: [PATCH v4 2/4] config.mak.uname: support for modern HPE NonStop config.

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 3, 2019, 19:45 UTC
Message-ID
<xmqqimz5h6et.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20181228200243.19728-1-randall.s.becker@rogers.com>
randall.s.becker@rogers.com writes:
Show 10 quoted lines
> @@ -470,8 +489,13 @@ ifeq ($(uname_S),NONSTOP_KERNEL)
>  	NO_MKDTEMP = YesPlease
>  	# Currently libiconv-1.9.1.
>  	OLD_ICONV = UnfortunatelyYes
> -	NO_REGEX = YesPlease
> +	NO_REGEX=NeedsStartEnd
>  	NO_PTHREADS = UnfortunatelyYes
>
>  	# Not detected (nor checked for) by './configure'.
>  	# We don't have SA_RESTART on NonStop, unfortunalety.

The hunk header claims that the preimage has 8 lines while the postimage has 13 lines, adding 5 new lines in total. But that is not what we can see in the hunk.

It is unclear to me if the numbers on the hunk header are bogus, or the patch text was truncated, so I cannot use these two patches with confidence. The first hunk had the same issue, and 1/4 too.

I do not see v4 3/4 and v4 4/4, either. It's not like you are the only person who sends patches to the mailing list, and not having the patches as responses to a cover letter for proper threading makes it very hard to see which patches belong to the same series and if all the necessary patches in a series have become available. Is it possible to arrange that to happen?

Thanks.
Previous: randall.s.becker@rogers.comNext: randall.s.becker@rogers.com
Message 2 of 4 in “config.mak.uname: support for modern HPE NonStop config.”
  1. 2/4 config.mak.uname: support for modern HPE NonStop config.randall.s.becker@rogers.com, Dec 28, 2018
  2. Junio C HamanoJan 3, 2019
  3. randall.s.becker@rogers.comJan 3, 2019
  4. Junio C HamanoJan 3, 2019

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.