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

Re: What's cooking in git.git (Jul 2019, #06; Thu, 25)

From
Elijah Newren <newren@gmail.com>
Date
Jul 27, 2019, 20:40 UTC
Message-ID
<CABPp-BEq+d=9G+U4im4fSEL2jGhggBwpoa+X7ZUjEGMPOPuFTw@mail.gmail.com>
In-Reply-To
<20190727193814.7400-1-rohit.ashiwal265@gmail.com>
Hi Rohit,
Let me attempt to answer on Junio's behalf...

On Sat, Jul 27, 2019 at 12:48 PM Rohit Ashiwal <rohit.ashiwal265@gmail.com> wrote:

Show 9 quoted lines
>
> Hi Junio
>
> On Thu, 25 Jul 2019 17:19:23 -0700 Junio C Hamano <gitster@pobox.com> wrote:
> >
> > * ra/rebase-i-more-options (2019-07-23) 4 commits
> >  - SQUASH???
>
> There are only 3 commits in this "series".

There are four, including Junio's commit he had to add in order to make the series merge with pu (a rename of your t3431 to the unoccupied t3433 slot). He labelled that commit "SQUASH???" and it's still quoted above. However, in general, when you submit the next round of your series, you should certainly include his fixups from his squash (or alternative fixes) inside your commits in order to get rid of the need for the squash commit.

Show 8 quoted lines
> >  - rebase -i: support --committer-date-is-author-date
> >  - sequencer: add NULL checks under read_author_script
> >  - rebase -i: add --ignore-whitespace flag
>
> The correct order should be:
>    - rebase -i: add --ignore-whitespace flag
>    - sequencer: add NULL checks under read_author_script
>    - rebase -i: support --committer-date-is-author-date

Are you thinking in order of application, or order that would be shown by `git log --oneline`? Junio includes the latter in his report.

> I'll soon send another revision and while on it, let's merge
> these topics into one. Should I also rebase them on the tip
> of git/git's master?

What do you mean by merge these topics into one? Do you mean merge all the commits into a single commit (which would be bad), or that your two original topics should be one, much like Junio already did?

In general, once submitted, avoid rebasing unless needed to integrate with someone else's work and clean up conflicts.

Hope that helps, Elijah

Previous: Rohit AshiwalNext: Rohit Ashiwal
Message 5 of 27 in “What's cooking in git.git (Jul 2019, #06; Thu, 25)”
  1. Junio C HamanoJul 26, 2019
  2. Johannes SchindelinJul 26, 2019
  3. Junio C HamanoJul 26, 2019
  4. Rohit AshiwalJul 27, 2019
  5. Elijah NewrenJul 27, 2019
  6. Rohit AshiwalJul 27, 2019
  7. Elijah NewrenJul 27, 2019
  8. Carlo ArenasJul 28, 2019
  9. Taylor BlauAug 9, 2019
  10. Ariadne ConillAug 9, 2019
  11. Taylor BlauAug 9, 2019
  12. Ariadne ConillAug 9, 2019
  13. Phil HordAug 9, 2019
  14. Ariadne ConillAug 9, 2019
  15. Taylor BlauAug 9, 2019
  16. Jeff KingAug 9, 2019
  17. Phil HordAug 9, 2019
  18. Randall S. BeckerAug 9, 2019
  19. Jeff KingAug 9, 2019
  20. Randall S. BeckerAug 9, 2019
  21. Junio C HamanoAug 9, 2019
  22. Phil HordAug 9, 2019
  23. Jeff KingAug 10, 2019
  24. Junio C HamanoAug 12, 2019
  25. Randall S. BeckerAug 12, 2019
  26. Junio C HamanoAug 9, 2019
  27. Randall S. BeckerAug 9, 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.