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

changing the set of dependencies (was: Branch dependencies)

From
MKmartin f krafft <madduck@madduck.net>
Date
Aug 3, 2011, 09:51 UTC
Message-ID
<20110803095103.GA27996@fishbowl.rw.madduck.net>
In-Reply-To
<CAKPyHN0EsXMKQ2g7ONaO4yw2ioPbMhg8XCsmB20je=O1DDeE5Q@mail.gmail.com>
also sprach Bert Wesarg <bert.wesarg@googlemail.com> [2011.08.03.0125 +0200]:
Show 11 quoted lines
> Not each feature branch may end up in master. And there does not need
> to be one feature branch which depends on all other features. For the
> latter you have probably an empty feature branch which just depends on
> all features. I call this branch mostly 'tip'. Removing a feature
> branch from the tips dependency list only with merges can't be done
> right now, and the proposed solutions never reached a usable state.
> 
> My second usecase is to convert a big quilt patch series into TopGit.
> Such big Quilt patches have mostly an artificial dependency to its
> predecessors. Removing these artifical dependencies makes it necessary
> to remove dependencies from patches.
Dear Bert, thank you for your reply.

Okay, understood. Yes, I agree entirely, the set of dependencies needs to be mutable. And they must not be invalidated by branch renames. Therefore, we really need some sort of other way to identify branches.

Is there a way other than lamenting that refs did not get UUIDs assigned to them from the early days onwards? ;)

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"if one cannot enjoy reading a book over and over again,
 there is no use in reading it at all."
                                                        -- oscar wilde
 
spamtraps: madduck.bogus@madduck.net
Previous: Bert WesargNext: martin f krafft
Message 5 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.