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

Re: [PATCH] git-cvsimport-script: handling of tags

From
HAH. Peter Anvin <hpa@zytor.com>
Date
Sep 6, 2005, 23:19 UTC
Message-ID
<431E2404.6060804@zytor.com>
In-Reply-To
<46a038f9050906155962d33869@mail.gmail.com>
Martin Langhoff wrote:
Show 8 quoted lines
> 
>>My style has always be to use tags for merges; tag the origin branch as
>>well as before and after on the receiving branch.
> 
> Do you move the tags with cvs tag -F? If that's the case, the data you
> need to merge is lost... otherwise, you could hack an alternative
> merge detection based on your tagnames.
> 
No, there are three tags:
             before-merge-foo
             |  after-merge-foo
             |  |
branch 1 ---*--*----
               /
              /
branch 2 ---*-------
             |
             merge-point-foo

That's why I was a bit confused. I thought most people did something similar.

	-hpa
Previous: Martin LanghoffNext: Junio C Hamano
Message 7 of 10 in “git-cvsimport-script: handling of tags”
  1. git-cvsimport-script: handling of tagsH. Peter Anvin, Sep 6, 2005
  2. H. Peter AnvinSep 6, 2005
  3. H. Peter AnvinSep 6, 2005
  4. Martin LanghoffSep 6, 2005
  5. H. Peter AnvinSep 6, 2005
  6. Martin LanghoffSep 6, 2005
  7. H. Peter AnvinSep 6, 2005
  8. Junio C HamanoSep 6, 2005
  9. Martin LanghoffSep 7, 2005
  10. H. Peter AnvinSep 7, 2005

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.