I certainly don't think the lib interface is anywhere near stable:
Linus accepted my change to index_fd far too easily.
Noted, thanks for the info.
(This makes a lot of sense, Git is evolving very fast. I haven't
looked at Git since mid-April, and I'm very much impressed at the
difference
[CC'd to the Git mailling list; please CC any replies to Darcs-Devel]
David, Ian,
I'd like to upgrade the Git code used in Darcs to 0.99 (we're
currently using 0.6). There are two good reasons for that, the first
of which is actually a showstopper:
- the format of Git repositories has changed
http://www.darcs.net/DarcsWiki/DarcsGit
You're welcome to leave any questions you might have -- I'll try to
answer.
Juliusz
-
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Aye, that will require some metadata on the git side (the hack,
suggested by Linus, of using git hashes to notice moves won't work).
So, why won't it work?
Because two files can legitimately have identical contents without
being ``the same'' file from the VC system's point of view.
In
[Removing Linus from CC, keeping the Git list -- or should we remove it?]
I'm not clear why it would be necesary, and it takes the only immutable
piece of information regarding a patch, and makes it variable.
Er... I'm not suggesting to make it variable, just to make it an
opaque blob of bytes
5 matches
Mail list logo