On Thu, Oct 14, 2010 at 20:00, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: > Ãvar ArnfjÃrà Bjarmason wrote: > >> Could you please pick up the 160 commit version of this at: >> >>   git://github.com/avar/git.git ab/i18n > > This is a "give an inch and they'll ask for a mile" sort of thing, but > would it be possible to maintain a stable branch with the i18n > infrastructure that only gets rebased when there is reorganization > going on? > > The gettextization and translations are rebased for other reasons (to > avoid going crazy), I know. ÂBut with the infrastructure it is starting > to be hard to track what changes over time. I could do that, but I've been hoping that it just gets picked up for the `next -> master` process of git.git itself and *that* becomes the stable target. But I have no idea what's going on at the other end, i.e. there's no comments about it in the "What's cooking in git.git" posts or elsewhere. So it's hard to know whether something like this is needed. It's been about as ready as it's ever going to get for about a month now. The libcharset.h change that was added to it a week or so ago could have come on top of the series. But since it hadn't been merged anywhere I rebased and inserted that earlier in the series for the relatively obscure case of helping bisectability on Windows. I'm starting to get the feeling that there isn't much interest in i18n support at all. It didn't show up highly in the wanted features in the Git survey, and most of the translations have been contributed by people I've poked directly. So maybe I should just get the hint and drop it *shrug*. I don't have much time to spend on this these days since I've been moving / starting a new job. So if it's not going to get merged into core I might as well do something else. (I'm not being bitter, really. Just practical) -- 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