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

Re: Rebase & submodules

From
RDRobert Dailey <rcdailey.lists@gmail.com>
Date
Sep 14, 2017, 17:46 UTC
Message-ID
<CAHd499BeANJBryo3sOoD2vT-A0M-R00GTa5-wTOumyj0EkSHkQ@mail.gmail.com>
In-Reply-To
<bf4275e5-ad96-4b71-e6a0-52c198cd541e@suse.de>

On Thu, Sep 14, 2017 at 10:57 AM, Nicolas Morey-Chaisemartin <NMoreyChaisemartin@suse.de> wrote:

> Without changing your workflow too much,

If you mean to imply that you have other recommendations if I'm willing to change my workflow, then please by all means share them. I'm very interested. I'm not too hooked on my workflow.

> simply add an annotated tag to your branch before your rebase.
> This way the SHA1 will always exists. Unless you want to cleanup at some point (branch merged ?) and then you can simply delete all those old tags.

This definitely the best idea so far; although the maintenance overhead of this could be high for long-lived branches with frequent rebases. Maybe with bigger workflow changes there are other solutions?

Previous: Nicolas Morey-Chaisemartin
Message 3 of 3 in “Rebase & submodules”
  1. Robert DaileySep 14, 2017
  2. Nicolas Morey-ChaisemartinSep 14, 2017
  3. Robert DaileySep 14, 2017

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.