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

Re: [PATCH v2 2/2] an improvement: removed configure.ac changes

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 23, 2024, 07:38 UTC
Message-ID
<xmqqmsrr1vhg.fsf@gitster.g>
In-Reply-To
<05df5d7e2d50cba77f53273c781f97d24144efc6.1708660111.git.gitgitgadget@gmail.com>
"Haritha D via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 11 quoted lines
> From: Haritha D <harithamma.d@ibm.com>
>
> Hello Reviewers, as an improvement, I have
> removed the CC_LD_DYNPATH changes because
> I was able to achieve the desired outcome
> by passing it to the make step.
>
> Signed-off-by: Haritha D <harithamma.d@ibm.com>
> ---
>  configure.ac | 3 ---
>  1 file changed, 3 deletions(-)

We frown upon a patch series that makes mistakes in an earlier step, only to fix them in a later step. The "git rebase -i" command helps us pretend to be more perfect developers than we actually are, whipping your patch series into a shape that builds one small step on top of another in a logical succession. Such a patch series is easier to understand than a history that faithfully records all the stumbles the developer made until they reached the final solution.

In this case, if you know before you sent these two patches that you do not need to touch configure.ac for CC_LD_DYNPATH at all, you can "git rebase -i" to whip the first patch into the desired shape, i.e. no changes to configure.ac, and drop this second patch, I think.

Show 14 quoted lines
> diff --git a/configure.ac b/configure.ac
> index 64569a80d53..d1a96da14eb 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -463,9 +463,6 @@ else
>              CC_LD_DYNPATH=-Wl,+b,
>            else
>               CC_LD_DYNPATH=
> -	     if test "$(uname -s)" = "OS/390"; then
> -		     CC_LD_DYNPATH=-L
> -	     fi
>               AC_MSG_WARN([linker does not support runtime path to dynamic libraries])
>            fi
>        fi
Previous: Haritha D via GitGitGadgetNext: Junio C Hamano
Message 8 of 18 in “This PR enables a successful git build on z/OS.”
  1. This PR enables a successful git build on z/OS.Haritha via GitGitGadget, Jan 31, 2024
  2. Kristoffer HaugsbakkJan 31, 2024
  3. Junio C HamanoJan 31, 2024
  4. Junio C HamanoJan 31, 2024
  5. 0/2 This PR enables a successful git build on z/OS.Haritha via GitGitGadget, Feb 23, 2024
  6. 1/2 build: support z/OS (OS/390).Haritha D via GitGitGadget, Feb 23, 2024
  7. 2/2 an improvement: removed configure.ac changesHaritha D via GitGitGadget, Feb 23, 2024
  8. Junio C HamanoFeb 23, 2024
  9. Junio C HamanoFeb 23, 2024
  10. build: support z/OS (OS/390).Haritha via GitGitGadget, Feb 25, 2024
  11. Junio C HamanoFeb 26, 2024
  12. Haritha DMar 1, 2024
  13. Ghanshyam ThakkarMar 1, 2024
  14. Junio C HamanoMar 1, 2024
  15. rsbecker@nexbridge.comMar 1, 2024
  16. Haritha DMar 4, 2024
  17. build: support z/OS (OS/390).Haritha via GitGitGadget, Mar 6, 2024
  18. Junio C HamanoMar 6, 2024

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.