>>>>> Lukas Czerner <lczerner@xxxxxxxxxx> writes: >>>>> On Mon, 15 Aug 2011, Ivan Shmakov wrote: BTW, the primary Git repository for the project is now located at Gitorious: git://gitorious.org/e2dis/e2dis-devel.git http://gitorious.org/e2dis/e2dis-devel.git https://gitorious.org/e2dis/e2dis-devel The most notable improvement that I made recently is that the payload message digests are now recorded. (The support for the whole-image and metadata message digests is not yet committed.) […] >> • moreover, I see no claims that the output of the debugfs(8) ‘stat’ >> command won't ever change (neither I see the formal description of >> the aforementioned output — its source is the only form of >> specification I could rely); my guess is that the C API, being >> documented, is going to be much more stable; > Well, you can probably say that about every tool, Why, there're plenty of tools that support either some sort of a standardized output, or output that's user-defined (based on some standardized items.) E. g., the output of ls(1) and date(1) is defined by POSIX (IEEE Std 1003.1-2008), etc. > but that is not good enough reason to duplicate the code for > everything. Although I am not saying that you're doing so. I believe that there's very little, if any, code duplication between e2dis and debugfs. […] -- FSF associate member #7257 Coming soon: Software Freedom Day http://mail.sf-day.org/lists/listinfo/ planning-ru (ru), sfd-discuss (en) -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
