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

Tracking parent branches in Git

From
EKEric Kulcyk <eric.kulcyk@microsoft.com>
Date
Jul 1, 2019, 18:50 UTC
Message-ID
<DM5PR00MB040845755401A07E5C90251CF1F90@DM5PR00MB0408.namprd00.prod.outlook.com>
Hello,
We would like to track parent branches so that creating pull requests can automatically determine the correct branch to merge against.  I understand that this would require tracking more information than is currently available right now in git.  Also, it seems that if some cases, it is not possible to determine a parent branch, in which case it would just be empty/null.  If I made a change to track the parent branch for each branch, would this feature be accepted/welcomed as part of git, even if it off by default?

Thanks, Eric

:(){:|:&};:
Next: Junio C Hamano
Message 1 of 13 in “Tracking parent branches in Git”
  1. Eric KulcykJul 1, 2019
  2. Junio C HamanoJul 1, 2019
  3. Bryan TurnerJul 1, 2019
  4. rsbecker@nexbridge.comJul 1, 2019
  5. Philip OakleyJul 2, 2019
  6. Junio C HamanoJul 2, 2019
  7. Bryan TurnerJul 2, 2019
  8. Theodore Ts'oJul 2, 2019
  9. Philip OakleyJul 3, 2019
  10. Eckhard MaaßJul 1, 2019
  11. Eric KulcykJul 1, 2019
  12. Eric KulcykJul 1, 2019
  13. Andreas KreyJul 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.