"Lars Hjemli" <hjemli@gmail.com> writes:Sorry, but libgit.a is not part of what we deliver. We do not support linking random stuff against libgit.a. We never did. It is not a "library". It has always been just an implementation detail for us to be lax about our Makefile, so that we do not have to write down exactly which *.o files git-foo command depended upon (and it is ceasing to be useful for that as very many things have moved to "the single git binary" these days). Instead we let the linker pick out the necessary pieces out of the archive. So, no, there is no breakage. The code movement you did _should_ not hurt so it may be a fine material for post 1.5.4, but I haven't carefully compared what other change might have accidentally snuck in that patch, and I would rather not have to during the rc cycle. - 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
| Justin C. Sherrill | Re: pkgsrc bulk build and tiff |
| Linus Torvalds | Linux 2.6.27-rc5 |
| Ingo Molnar | [crash, bisected] Kernel BUG at ffffffff8079afb1 (__netif_schedule()) |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Evgeniy Polyakov | Re: tbench wrt. loopback TSO |
