On Tue, 10 Apr 2007, Andy Parkins wrote:this is very similar to the problem I asked about with merging config files a couple weeks ago. the answer then was that when we get .gitattributes we should be able to specify content specific merge programs that could deal with this sort of thing on a per-file basis. That sounds like the answer to your concern as well, rather then makeing things order dependant and otherwise harder to read to make it able to be merged with the current tools (which assume line-based order-dependant content) David Lang - 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
| Zhang, Yanmin | AIM7 40% regression with 2.6.26-rc1 |
| Con Kolivas | [PATCH][RSDL-mm 0/7] RSDL cpu scheduler for 2.6.21-rc3-mm2 |
| Nick Piggin | [patch 4/6] mm: merge populate and nopage into fault (fixes nonlinear) |
| Andrew Morton | -mm merge plans for 2.6.23 |
git: | |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Natalie Protasevich | [BUG] New Kernel Bugs |
