From: Michael P. <mic...@gm...> - 2010-12-08 02:35:34
|
Segher Boessenkool wrote: >> > With modifications in the tarball, unless you have changed your mind and >> > now >> > support listing nearly every file in .gitattributes. >> >> I'm not sure what you're saying here. The tarball will have plain LF >> for everything since that's how stuff appears in the repo. And I was requesting a version be available that is crlf, since tar does not have an autocrlf option last I checked like git does. If the crlf version is zip and the lf version is tgz, that would be very natural. But I hope you're not claiming the only way to put crlf's into the snapshot is to also have them in git. My point is that I was already aware of the link you pointed to on gitweb, and I don't think that satisfies the criteria I've listed, or even one of the ones you listed (autogen). >> (except msvc project files and "binary" stuff like that), Ok, this is a tangent, but the msvc files are "text", unless you're reversing your opinion from what you said earlier: "A 'text' file, from the user's point of view, is anything that is, well, text: documentation files, C source files, build system files, etc." There you go, build system files. >> >>> [...] do not require you >> >>> to have (the correct version of) autotools installed, etc. >> > >> > That too, but per commit. >> >> Not sure what you say here either -- you want a "release snapshot" >> for every commit? Well, every commit on master? Dunno about the "release" part, but yes snapshot. We have discussed in the past having this available per commit on any repo, particularly Pete's. And really I'm just advocating for what I would want if I weren't already involved with libusb (and therefore using my git repo); in a sense, I won't lose a whole lot of sleep if the snapshots do not become available, but I figure there might be users out there who would want something similar. I also have no interest in binaries, but I'm in the minority on that one. Regards, Michael |