| 1 |
Alexander Holler wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> --On Sonntag, Juni 09, 2002 20:54:50 -0400 Marko Mikulicic |
| 5 |
> <marko@××××.org> wrote: |
| 6 |
> |
| 7 |
>> The CVS docs state that there is no way to selectively |
| 8 |
>> disable kw substitution, but alternatively, couldn't the skel |
| 9 |
>> files be committed as binary files. I suppose that there wouln't be many |
| 10 |
>> changes to those files, and they are small. It isn't a big deal, but it |
| 11 |
>> confuses new users like me. |
| 12 |
>> Comments ? |
| 13 |
> |
| 14 |
> |
| 15 |
> checkin with -ko. |
| 16 |
|
| 17 |
yes but is not selective; it applies to all files. |
| 18 |
|
| 19 |
> |
| 20 |
> Alexander |
| 21 |
> |
| 22 |
> PS: it seems The $Header etc. are getting lost anywhere from the way out |
| 23 |
> of the cvs to the rsync. Maybe there's some shell script which |
| 24 |
> interprets those files (recognizing $Header and $ as variables and |
| 25 |
> replacing them with zero content) |
| 26 |
|
| 27 |
as pointed out by Karl is probably not CVS's fault. |
| 28 |
But still I don't understand how you can put a file |
| 29 |
containing a keyword in CVS without being substituted |
| 30 |
and having another file in the same repository to which this |
| 31 |
doesn't apply. All docs I read about CVS stated that they own |
| 32 |
documentation used some forms of escape (ex: @asis{} in texinfo) |
| 33 |
to avoid it in the examples. How is it solved in the skel ? |
| 34 |
|
| 35 |
Marko |
Archives