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

Re: Branch dependencies

From
MKmartin f krafft <madduck@madduck.net>
Date
Aug 2, 2011, 19:08 UTC
Message-ID
<20110802190806.GA16674@fishbowl.rw.madduck.net>
In-Reply-To
<CAKPyHN0kAJ-MVsrXam5NjsOYkta4nsSrZUvKoMSi-FeRUSuLEw@mail.gmail.com>
also sprach Bert Wesarg <bert.wesarg@googlemail.com> [2011.08.02.1506 +0200]:
Show 5 quoted lines
> while I appreciate, that you dig this topic up. I think you are trying
> to solve the wrong problem first. My main problem with the TopGit
> approach is, that you can't freely change the dependencies of a topic.
> This may be not the most common case in distro development. But in my
> eyes more problematic than maintaining the meta data.
Hello Bert, thank you for taking the time to respond!

Could you please try to illuminate me a bit on a use-case of changing dependencies? I am aware that TopGit has had a problem with changing dependencies due to renamed branches, and I think I have a solution to that (encode the dependent ref, not the branch head), but I cannot come up with a use case for freely changing dependencies just like that.

> For my first mentioned problem, I think a new 'system' needs to be
> 'rebase' based, not merge based like TopGit.
The problem with rebasing is that you cannot publish the branches.

However, maybe I am simply not seeing the light here. Do you have some further ideas about what this would be like? Please keep in mind that what I seek is not just a way to bring feature branches up-to-date with upstream, but also to have those branches be shared among developers.

Thanks,
-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"gott ist tot! und wir haben ihn getötet."
                                                 - friedrich nietzsche
 
spamtraps: madduck.bogus@madduck.net
Previous: Bert WesargNext: Bert Wesarg
Message 3 of 8 in “Branch dependencies”
  1. martin f krafftAug 1, 2011
  2. Bert WesargAug 2, 2011
  3. martin f krafftAug 2, 2011
  4. Bert WesargAug 2, 2011
  5. changing the set of dependencies (was: Branch dependencies)martin f krafft, Aug 3, 2011
  6. TopGit with rebased branches, problems with publishing (was: Branch dependencies)martin f krafft, Aug 3, 2011
  7. Tracking topic branches with rebases vs. merges (was: Branch dependencies)martin f krafft, Aug 3, 2011
  8. Nicolas SebrechtAug 4, 2011

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.