Martin Koegler wrote:I know that it's not, which is why I'm doing research to take care of the pieces interesting for libgit2 that could possibly have been derived from elsewhere. Reading and filling structures specific to git is something I'd be surprised if they originated outside of git though. Right, but if we can never re-use code from git.git, libgit will never fly. It's unfortunately as simple as that. So perhaps we're left with the option of writing a GPL'd library or just go hang. To a certain point, "git blame" can. Right. If possible, I'd still like an OK from you though. If nothing else, it'll make it possible to re-use code that originated from someone else and that you changed, assuming that "someone else" also agree to relicensing their code. With 100% of the authors agreeing to that, we could have a libified git flying in a matter of months instead of never. It's unfortunate if the letter of the law pertaining to a particular license should prevent the copyright owners from doing whatever they want with the code, but perhaps that's the world we live in. -- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 -- 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 Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Linus Torvalds | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Andrew Morton | 2.6.25-mm1 |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| David Miller | [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| Natalie Protasevich | [BUG] New Kernel Bugs |
