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

Linear history *and* share a branch?

From
HWHilco Wijbenga <hilco.wijbenga@gmail.com>
Date
Apr 5, 2012, 20:48 UTC
Message-ID
<CAE1pOi0-uSaQwgJHMTkw3nqp=idxZxMbyfKtLni0=Xwu-L-_hA@mail.gmail.com>
Hi all,

We have been using Git for about a year now in a very small team. So far, everyone has worked on their own local branches and been doing "git rebase master" to make sure their local branches stay in synch. This way we have a nice linear history in master.

Recently, it has become useful to share one of these local branches between two devs. Of course, when one of the devs does his usual "git rebase master", he screws up the other dev's environment. Our solution has been to keep rebasing the shared branch but to actually work on a local branch that is rebased on the shared branch. By judiciously using "git reset" and "git pull" on the shared branch the two devs can keep the shared branch in synch and then use "git rebase shared-branch" on their local branch to keep it in synch to. While this works, there is probably a better/simpler solution.

Should we simply do "git merge master" instead of "git rebase master"? And then do something at the end when we are about to merge the shared branch back into master to guarantee linear history? Your thoughts and ideas would be greatly appreciated.

Cheers, Hilco

Next: Ævar Arnfjörð Bjarmason
Message 1 of 7 in “Linear history *and* share a branch?”
  1. Hilco WijbengaApr 5, 2012
  2. Ævar Arnfjörð BjarmasonApr 5, 2012
  3. Ævar Arnfjörð BjarmasonApr 6, 2012
  4. Junio C HamanoApr 5, 2012
  5. Hilco WijbengaApr 5, 2012
  6. Michael WittenApr 6, 2012
  7. Neal KreitzingerApr 10, 2012

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.