[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lmi] Should we restrict cvs files to ASCII?
From: |
Greg Chicares |
Subject: |
[lmi] Should we restrict cvs files to ASCII? |
Date: |
Tue, 17 Apr 2007 12:50:12 +0000 |
User-agent: |
Thunderbird 1.5.0.10 (Windows/20070221) |
I see this inadvertent change:
ChangeLog,v 1.618 2007/04/17 12:33:09
- "§21.2206(1)(I)-(M), (O), (Q)-(S) and (U)-(V) Supplemental - Other"
+ "�21.2206(1)(I)-(M), (O), (Q)-(S) and (U)-(V) Supplemental - Other"
I'm not sure how that'll show up in email, but
I can see it here:
http://cvs.savannah.gnu.org/viewcvs/lmi/lmi/ChangeLog?sortby=date&r2=1.618&r1=1.617
How do other projects typically prevent this?
Should we just restrict all files in cvs to ASCII?
For now, I'll revert that one line.
- [lmi] Should we restrict cvs files to ASCII?,
Greg Chicares <=
- Re: [lmi] Should we restrict cvs files to ASCII?, Vadim Zeitlin, 2007/04/17
- Re: [lmi] Should we restrict cvs files to ASCII?, Greg Chicares, 2007/04/17
- Re: [lmi] Should we restrict cvs files to ASCII?, Evgeniy Tarassov, 2007/04/17
- Re[2]: [lmi] Should we restrict cvs files to ASCII?, Vadim Zeitlin, 2007/04/17
- Re: Re[2]: [lmi] Should we restrict cvs files to ASCII?, Evgeniy Tarassov, 2007/04/17
- Re: Re[2]: [lmi] Should we restrict cvs files to ASCII?, Evgeniy Tarassov, 2007/04/17
- Re[4]: [lmi] Should we restrict cvs files to ASCII?, Vadim Zeitlin, 2007/04/17
Re: [lmi] Should we restrict cvs files to ASCII?, Evgeniy Tarassov, 2007/04/17