> Is your conversion two-way? IOW, is it possible to convert the > converted file and get the original? (Because all the existing > conversions are reversible) Yes and no. The CRLF conversion isn't always invertable—it is so long as your use of CRLF/LF is consistent. The tab/space conversion is similar: if you consistently use spaces, then tabs_to_spaces will always give you back your original version; if you consistently use tabs, then spaces_to_tabs will give you back your original version. If you use some crazy mix of the two, you cannot reconstruct your original without remembering where there were tabs versus spaces, which information either filter destroys. But that's the same as the CRLF conversion. You could enable a warning when worktree file has an inconsistent mixture of tabs and spaces, like there is for inconsistent CRLF files. On Tue, Oct 14, 2008 at 11:25 PM, Alex Riesen <raa.lkml@xxxxxxxxx> wrote: > Stefan Karpinski, Wed, Oct 15, 2008 03:44:10 +0200: >> I find myself really wanting to enforce standards in the use of spaces >> versus tabs. I deal with some unruly programmers who refuse to set >> their editors to use soft tabs, but I *hate* tabs in the repo. And of >> course others feel equally strongly about keeping only tabs in the >> repo (e.g. the git repo). >> >> This led me to wonder if it wouldn't make sense to have this >> conversion ability built into git. The following patch implements this >> functionality. It still needs work—it's not meant to be final, just to >> give an idea—but I just wanted to see if people on the git list >> thought this sort of thing would be worthwhile at all. > > Is your conversion two-way? IOW, is it possible to convert the > converted file and get the original? (Because all the existing > conversions are reversible) > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
