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

Re: branch versioning

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Oct 4, 2010, 13:29 UTC
Message-ID
<AANLkTi=73Siu9O1WT8MdjfAEO5j5y=CkOAiof0z83L=c@mail.gmail.com>
In-Reply-To
<AANLkTimWxPPi_hHuato+hHePaEja=66GzLEpDUVcZV0i@mail.gmail.com>
On Mon, Oct 4, 2010 at 13:18, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
Show 5 quoted lines
> How do you guys manage versions of a topic branch? I usually end up
> saving format-patch series somewhere or forget all old versions.
> Although I really want to keep old versions around. reflog to me   is
> polluted with every kind of branch updates. And it's local
> information. It can't be transferred to another repo (or can it?)

I usually have foo, foo-v2, foo-v3 which eventually gets reset back to foo once I'm sure nobody cares about the initial one or foo-v2. It's very chaotic.

So my git.git on GitHub is up to 123 branches, and I don't even want to know what my personal git.git is at. I also save my outgoing format-patch E-Mails, but would probably do less of that if there was support for attaching the comments after the diffstat in a git-note or something.

Previous: Matthieu MoyNext: Nguyen Thai Ngoc Duy
Message 3 of 8 in “branch versioning”
  1. Nguyen Thai Ngoc DuyOct 4, 2010
  2. Matthieu MoyOct 4, 2010
  3. Ævar Arnfjörð BjarmasonOct 4, 2010
  4. Nguyen Thai Ngoc DuyOct 4, 2010
  5. Ævar Arnfjörð BjarmasonOct 4, 2010
  6. Michael J GruberOct 4, 2010
  7. Nguyen Thai Ngoc DuyOct 4, 2010
  8. Tomas CarneckyOct 4, 2010

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.