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

Re: Multi-ancestor read-tree notes

From
Fredrik Kuivinen <freku045@student.liu.se>
Date
Sep 8, 2005, 20:37 UTC
Message-ID
<20050908203756.GB26088@c165.ib.student.liu.se>
In-Reply-To
<1126199765.3984.1.camel@localhost.localdomain>
On Thu, Sep 08, 2005 at 12:16:05PM -0500, Darrin Thompson wrote:
Show 7 quoted lines
> On Mon, 2005-09-05 at 01:41 -0400, Daniel Barkalow wrote:
> > I've got a version of read-tree which accepts multiple ancestors and does 
> > a merge using information from all of them.
> 
> Do the multiple ancestors have to share a common parent? More to the
> point, is this read-tree any more friendly to baseless merges?
> 

Is a baseless merge a merge with two branches that do not have a common ancestor? That is, if we want to merge the branches A and B and git-merge-base --all A B do not return any commits, is that a baseless merge?

If that is the case then my merge code handles baseless merges fine. Or, it is _supposed_ to handle them, I have done some basic tests but it hasn't been tested thoroughly yet.

I don't know how the new read-tree code handles those cases.
- Fredrik
Previous: Darrin ThompsonNext: Daniel Barkalow
Message 11 of 18 in “Multi-ancestor read-tree notes”
  1. Daniel BarkalowSep 5, 2005
  2. Junio C HamanoSep 6, 2005
  3. Daniel BarkalowSep 6, 2005
  4. Junio C HamanoSep 6, 2005
  5. Daniel BarkalowSep 6, 2005
  6. Junio C HamanoSep 6, 2005
  7. Daniel BarkalowSep 6, 2005
  8. Junio C HamanoSep 10, 2005
  9. Junio C HamanoSep 10, 2005
  10. Darrin ThompsonSep 8, 2005
  11. Fredrik KuivinenSep 8, 2005
  12. Daniel BarkalowSep 8, 2005
  13. Darrin ThompsonSep 8, 2005
  14. Junio C HamanoSep 8, 2005
  15. Daniel BarkalowSep 8, 2005
  16. Junio C HamanoSep 9, 2005
  17. Daniel BarkalowSep 9, 2005
  18. Matthias UrlichsSep 11, 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.