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

Re: [RFC/PATCH 2/2] rebuash - support for status

From
Edmundo Carmona Antoranz <eantoranz@gmail.com>
Date
Jun 30, 2019, 05:28 UTC
Message-ID
<CAOc6etazOEvDmEKp7ABV+GoqPoO+Z92oQazyt56rRBDBnyk6ZQ@mail.gmail.com>
In-Reply-To
<20190630051816.8814-2-eantoranz@gmail.com>

On Sat, Jun 29, 2019 at 11:18 PM Edmundo Carmona Antoranz <eantoranz@gmail.com> wrote:

Show 6 quoted lines
>
> ---
>  wt-status.c | 49 +++++++++++++++++++++++++++++++++++++++++++------
>  wt-status.h |  1 +
>  2 files changed, 44 insertions(+), 6 deletions(-)
>
I bet there are more things to do... like:
- what happens if the user runs git checkout --force some-branch? The
state file has to be deleted, right?
- what should happen on the reflog when there's the merge then reset?
Is it possible to control what will show up on the reflog from the
script?

So any guiding word on the things I should take a look at would be greatly appreciated.

Previous: Edmundo Carmona AntoranzNext: Jeff King
Message 3 of 13 in “rebuash - squash/rebase in a single step”
  1. 1/2 rebuash - squash/rebase in a single stepEdmundo Carmona Antoranz, Jun 30, 2019
  2. 2/2 rebuash - support for statusEdmundo Carmona Antoranz, Jun 30, 2019
  3. Edmundo Carmona AntoranzJun 30, 2019
  4. Jeff KingJun 30, 2019
  5. Edmundo Carmona AntoranzJun 30, 2019
  6. Jeff KingJun 30, 2019
  7. Edmundo Carmona AntoranzJul 1, 2019
  8. Junio C HamanoJul 1, 2019
  9. Edmundo Carmona AntoranzJul 1, 2019
  10. Junio C HamanoJul 1, 2019
  11. Derrick StoleeJul 2, 2019
  12. Junio C HamanoJul 2, 2019
  13. Johannes SixtJul 2, 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.