On 2008-06-19 10:33:56 +0200, Miklos Vajna wrote:What you're describing is pretty much what we're thinking about doing -- have a log branch where each commit contains enough metadata to recreate the complete patch stack state at that point in time, and has all the parents it needs to be safe from gc. The particular problem I'm asking about here is that due to StGit's concept of "unapplied" patches that are per definition not reachable from the current branch head, a given log entry might have to keep an unbounded number of commits from being gc'ed. Thus my question about what would blow up if we were to make a commit with 50 parents. Or 100. Or 1000, if our users are crazy enough. (The alternative being, of course, to make a tree of octopuses with a fixed maximum fan-out.) -- Karl Hasselström, kha@treskal.com www.treskal.com/kalle -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Martin Michlmayr | Network slowdown due to CFS |
| Ingo Molnar | Re: x86 arch updates also broke s390 |
git: | |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
