You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by "Roy T. Fielding" <fi...@liege.ICS.UCI.EDU> on 1996/08/04 11:39:11 UTC
Re: cvs commit: apache/conf mime.types
okay, so why did it say
Bad avail line: unavai
Vi's standard input and output must be a terminal.
Log message unchanged or not specified
a)bort, c)ontinue, e)dit, !)reuse this message unchanged for remaining dirs
Action: (continue) Checking in mime.types;
/export/home/cvs/apache/conf/mime.types,v <-- mime.types
new revision: 1.5; previous revision: 1.4
done
Mailing the commit message...
after I edited the log message? It apparently worked fine, but I've
never seen this response from a local commit. I am assuming it is
part of the remote commit actions, and the part about the Log message
being unchanged is due to my mistake of placing the log text after the
Submitted-by line instead of before it, but the "Bad avail line" does
not give me the warm fuzzies. :(
.....Roy
Re: cvs commit: apache/conf mime.types
Posted by Paul Richards <p....@elsevier.co.uk>.
Alexei Kosut <ak...@nueva.pvt.k12.ca.us> writes:
>
> On Sun, 4 Aug 1996, Roy T. Fielding wrote:
>
> > okay, so why did it say
> >
> > Bad avail line: unavai
>
> Because Paul (I think) mispelled unavail in the avail file. Someone should
> probably fix it. But it doesn't hurt anything.
Uhh, yeah, fixed now. Harmless warning as far as commits are
concerned.
> > Vi's standard input and output must be a terminal.
>
> This comes about because cvs server has to do weird things with vi
> and rcs to check in a file. I'm not sure exactly what, but it does it
> every time. It's normal.
Was this a remote commit? I'm not sure why but vi complains when doing
a remote commit and the cvsedit script has had the checking of the
return code disabled.
You can safely ignore the error, the remote cvs access isn't fully
smoothed out yet since not all of the local functionality can be
implemented remotely. It doesn't affect the integrity of the
repository, just some of the nicer trappings provided by the scripts
don't work as well.
--
Paul Richards. Originative Solutions Ltd. (Netcraft Ltd. contractor)
Elsevier Science TIS online journal project.
Email: p.richards@elsevier.co.uk
Phone: 0370 462071 (Mobile), +44 (0)1865 843155
Re: cvs commit: apache/conf mime.types
Posted by Alexei Kosut <ak...@nueva.pvt.k12.ca.us>.
On Sun, 4 Aug 1996, Roy T. Fielding wrote:
> okay, so why did it say
>
> Bad avail line: unavai
Because Paul (I think) mispelled unavail in the avail file. Someone should
probably fix it. But it doesn't hurt anything.
> Vi's standard input and output must be a terminal.
>
> Log message unchanged or not specified
> a)bort, c)ontinue, e)dit, !)reuse this message unchanged for remaining dirs
This comes about because cvs server has to do weird things with vi
and rcs to check in a file. I'm not sure exactly what, but it does it
every time. It's normal.
> Action: (continue) Checking in mime.types;
> /export/home/cvs/apache/conf/mime.types,v <-- mime.types
> new revision: 1.5; previous revision: 1.4
> done
> Mailing the commit message...
This should be self-explanatory. It started to check in the file,
tells you what the filename is, what revision you are checking in, it
finished, and then it mails a message.
--
________________________________________________________________________
Alexei Kosut <ak...@nueva.pvt.k12.ca.us> The Apache HTTP Server
URL: http://www.nueva.pvt.k12.ca.us/~akosut/ http://www.apache.org/