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

Re: [PATCH v3 6/7] rebase: write better reflog messages

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 24, 2013, 03:26 UTC
Message-ID
<7vfvw8dw9m.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1371629089-27008-7-git-send-email-artagnon@gmail.com>
Ramkumar Ramachandra <artagnon@gmail.com> writes:
Show 8 quoted lines
> @@ -59,6 +63,9 @@ else
>  		return $?
>  	fi
>  
> +	# always reset GIT_REFLOG_ACTION before calling any external
> +	# scripts; they have no idea about our base_reflog_action
> +	GIT_REFLOG_ACTION="$base_reflog_action"
>  	git am $git_am_opt --rebasing --resolvemsg="$resolvemsg"
Why does this reroll still use this base_reflog_action convention?

The original orig_reflog_action you borrowed this may have been an acceptable local solution inside git-rebase--interactive that does not call out to amyting, but the above comment a good demonstration that shows why this cannot be a good general solution that scales across scriptlets.

And I already explained that to you at least twice.
cf. http://article.gmane.org/gmane.comp.version-control.git/228399
    But after writing it down this way, I realize that introduction of
    base_reflog_action (or GIT_REFLOG_NAME which is a moral equivalent)
    is not helping us at all.  As long as calls to "git" command in the
    second category exists in these scripts, GIT_REFLOG_ACTION *must* be
    kept pristine after set_reflog_action sets it, so we can get rid of
    this new variable, and rewrite 3.a and 3.b like so:
        3-a)
            GIT_REFLOG_ACTION="$GIT_REFLOG_ACTION: custom message" \
                    git cmd
        3-b)
            SAVED=$GIT_REFLOG_ACTION
            GIT_REFLOG_ACTION="$GIT_REFLOG_ACTION: custom message"
            output git cmd
            GIT_REFLOG_ACTION=$SAVED
                or
            (
                    GIT_REFLOG_ACTION="$GIT_REFLOG_ACTION: custom message"
                    output git cmd
            )
    That essentially boils down to the very original suggestion I made
    before Ram introduced the base_reflog_action.
Previous: Ramkumar RamachandraNext: Ramkumar Ramachandra
Message 10 of 14 in “Re-roll rr/rebase-checkout-reflog”
  1. 0/7 Re-roll rr/rebase-checkout-reflogRamkumar Ramachandra, Jun 19, 2013
  2. 1/7 t/t7512-status-help: test "HEAD detached from"Ramkumar Ramachandra, Jun 19, 2013
  3. 2/7 wt-status: remove unused field in grab_1st_switch_cbdataRamkumar Ramachandra, Jun 19, 2013
  4. 3/7 t/t2012-checkout-last: test "checkout -" after a rebaseRamkumar Ramachandra, Jun 19, 2013
  5. Johannes SixtJun 19, 2013
  6. Ramkumar RamachandraJun 19, 2013
  7. 4/7 status: do not depend on rebase reflog messagesRamkumar Ramachandra, Jun 19, 2013
  8. 5/7 checkout: respect GIT_REFLOG_ACTIONRamkumar Ramachandra, Jun 19, 2013
  9. 6/7 rebase: write better reflog messagesRamkumar Ramachandra, Jun 19, 2013
  10. Junio C HamanoJun 24, 2013
  11. Ramkumar RamachandraJun 24, 2013
  12. Junio C HamanoJun 24, 2013
  13. Ramkumar RamachandraJun 24, 2013
  14. 7/7 rebase -i: write better reflog messagesRamkumar Ramachandra, Jun 19, 2013

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.