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

Re: [PATCH 1/2] rebase -i: support --root without --onto

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 26, 2012, 19:20 UTC
Message-ID
<7vtxxxc22x.fsf@alter.siamese.dyndns.org>
In-Reply-To
<bdb45972685db8899a46ebc62213e56c9a3d0c94.1340717793.git.chris@arachsys.com>
Chris Webb <chris@arachsys.com> writes:
> +do_pick () {
> +	if test "$(git rev-parse HEAD)" = "$squash_onto"

The idea to create a sentinel root upfront and special case it here is a good one.

> +	then
I am not quite sure what is going on in this "then" clause.
> +		git commit --allow-empty --allow-empty-message --amend \
> +			   --no-post-rewrite -n -q -C $1 &&

At this point, nobody touched the empty sentinel root yet; you rewrite its log message and authorship using the picked commit.

> +			pick_one -n $1 &&

And then you create a new commit that records the update "$1" does relative to its parent (this hopefully only contains additions -- is it sensible to die-with-patch if it doesn't?), making sure that it does not fast-forward. Does this always make the result a root commit? If "$1" has parents, wouldn't it become a child of the commits its parents were rewritten to (if any) in pick_one_preserving_merges() that is called from pick_one?

> +			git commit --allow-empty --allow-empty-message \
> +				   --amend --no-post-rewrite -n -q -C $1 ||
And then you rewrite the log and authorship of that one.
In short, my questions are:
 (1) what is the purpose of the first "commit --amend" to update the
     sentinel root commit?
 (2) Is the purpose of "pick_one -n" done here to create a root
     commit?  Does it always do so correctly?
Show 22 quoted lines
> diff --git a/git-rebase.sh b/git-rebase.sh
> index e616737..bde2be8 100755
> --- a/git-rebase.sh
> +++ b/git-rebase.sh
> @@ -31,7 +31,7 @@ SUBDIRECTORY_OK=Yes
>  OPTIONS_KEEPDASHDASH=
>  OPTIONS_SPEC="\
>  git rebase [-i] [options] [--onto <newbase>] [<upstream>] [<branch>]
> -git rebase [-i] [options] --onto <newbase> --root [<branch>]
> +git rebase [-i] [options] [--onto <newbase>] --root [<branch>]
>  git-rebase [-i] --continue | --abort | --skip
>  --
>   Available options are
> @@ -364,6 +364,11 @@ and run me again.  I am stopping in case you still have something
>  valuable there.'
>  fi
>  
> +if test -n "$rebase_root" && test -z "$onto"
> +then
> +	test -z "$interactive_rebase" && interactive_rebase=implied
> +fi
> +

This makes "git rebase --root" without $onto imply "-i", which makes sense, but it was a bit unexpected (it wasn't in the proposed log message).

Previous: Chris WebbNext: Chris Webb
Message 20 of 29 in “Editing the root commit”
  1. Chris WebbJun 19, 2012
  2. Junio C HamanoJun 19, 2012
  3. Chris WebbJun 19, 2012
  4. Chris WebbJun 20, 2012
  5. Junio C HamanoJun 20, 2012
  6. Jeff KingJun 20, 2012
  7. Chris WebbJun 20, 2012
  8. Jeff KingJun 20, 2012
  9. Chris WebbJun 22, 2012
  10. Junio C HamanoJun 22, 2012
  11. Chris WebbJun 22, 2012
  12. Chris WebbJun 22, 2012
  13. Junio C HamanoJun 22, 2012
  14. Chris WebbJun 23, 2012
  15. git-commit bug (was Re: Editing the root commit)Chris Webb, Jun 26, 2012
  16. git-checkout: disallow --detach on unborn branchChris Webb, Jun 26, 2012
  17. Junio C HamanoJun 26, 2012
  18. Chris WebbJun 26, 2012
  19. 1/2 rebase -i: support --root without --ontoChris Webb, Jun 26, 2012
  20. Junio C HamanoJun 26, 2012
  21. Chris WebbJun 26, 2012
  22. Junio C HamanoJun 26, 2012
  23. Chris WebbJun 26, 2012
  24. Junio C HamanoJun 26, 2012
  25. Chris WebbJun 26, 2012
  26. 2/2 Add tests for rebase -i --root without --ontoChris Webb, Jun 26, 2012
  27. Chris WebbJun 20, 2012
  28. Martin von ZweigbergkJun 25, 2012
  29. jaseem abidJun 19, 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.