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

Re: [PATCH] Warnings before rebasing -i published history

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Jun 7, 2012, 22:04 UTC
Message-ID
<vpqy5ny22z5.fsf@bauges.imag.fr>
In-Reply-To
<1339104053-7782-1-git-send-email-Lucien.Kong@ensimag.imag.fr>
Lucien Kong <Lucien.Kong@ensimag.imag.fr> writes:
> For now, the code only warns the user; he can't revert back to his
> original state. We agree with everyone that he should be given a
> way to abort the rebase.
He already has: empty the todo-list in the editor and you're done.
Show 9 quoted lines
> +warn_published () {
> +	cat "$1" | while read -r command sha1 message
> +	do
> +		test -n "$sha1" || break
> +		if test -n "$(git branch -r --contains "$sha1")"
> +		then
> +			printf "%s\n" "$(sed -e "/"$sha1"/ s|$| [Published]|" "$1")" >"$1"
> +		fi
> +	done

Aren't you reading and writing from the same file here? Sounds dangerous.

This appends [Published] to commits that are reachable from a remote-tracking branch, but I'm wondering if actually showing the remote branch name wouldn't be better, e.g.

pick <id> commit one # Commits above this line appear in origin/master pick <id> commit two pick <id> commit three # Commits above this line appear in origin/next pick <id> most recent commit

>  test -s "$todo" || echo noop >> "$todo"
>  test -n "$autosquash" && rearrange_squash "$todo"
> +warn_published "$todo"
That should be configurable.
Show 5 quoted lines
> @@ -869,6 +884,8 @@ cat >> "$todo" << EOF
>  #  f, fixup = like "squash", but discard this commit's log message
>  #  x, exec = run command (the rest of the line) using shell
>  #
> +# Warning: [Published] means that the commit has already been published

It's a pity to show the message unconditionally. If you go this way, skip the message if you didn't display [Published].

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Lucien KongNext: konglu@minatec.inpg.fr
Message 2 of 25 in “Warnings before rebasing -i published history”
  1. Warnings before rebasing -i published historyLucien Kong, Jun 7, 2012
  2. Matthieu MoyJun 7, 2012
  3. konglu@minatec.inpg.frJun 8, 2012
  4. Matthieu MoyJun 8, 2012
  5. Junio C HamanoJun 8, 2012
  6. Junio C HamanoJun 7, 2012
  7. konglu@minatec.inpg.frJun 8, 2012
  8. Matthieu MoyJun 8, 2012
  9. Tomas CarneckyJun 8, 2012
  10. Matthieu MoyJun 8, 2012
  11. Junio C HamanoJun 8, 2012
  12. [PATCHv2] Warnings before rebasing -i published historyLucien Kong, Jun 11, 2012
  13. Matthieu MoyJun 11, 2012
  14. konglu@minatec.inpg.frJun 11, 2012
  15. Matthieu MoyJun 11, 2012
  16. branch --contains is unbearably slow [Re: [PATCHv2] Warnings before rebasing -i published history]Thomas Rast, Jun 11, 2012
  17. Junio C HamanoJun 11, 2012
  18. Thomas RastJun 11, 2012
  19. Thomas RastJun 11, 2012
  20. Junio C HamanoJun 11, 2012
  21. 1/2 Warnings before rebasing -i published historyLucien Kong, Jun 11, 2012
  22. 2/2 Warnings before amending published historyLucien Kong, Jun 11, 2012
  23. Matthieu MoyJun 12, 2012
  24. Junio C HamanoJun 12, 2012
  25. Nguy ThomasJun 12, 2012

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.