Doug Morris <[EMAIL PROTECTED]> writes:
> I've created a subdirectory "docs" in the nmh sources and moved most
> of the files that were In the top level into it. The sources were
> getting pretty messy. Anyone working with the cvs versions should
> probablly do
>
> cvs update -d
>
> to bring your local copy in sync.
Umm... wish you hadn't done that. You broke the URL I gave in my 1.0.4
announce message:
> A detailed description of the changes between 1.0.3 and 1.0.4 is available
> from:
>
> http://www.mhost.com/cgi-bin/cvsweb/nmh/ChangeLog?r1=1.40&r2=1.71
It also sucks to lose the version history on all those files. I also don't
think that some of them should go in docs/. I agree that it was getting
somewhat crowded at the top-level, but it's pretty common practice in UNIX
source packages to do things that way. Certainly all files relating to
building nmh (like MACHINES) should go at the top level, I think.
Okay, I just ssh'd into my account on mhost.com and undeleted ChangeLog in
the top directory (lame that cvs doesn't give you a way to do that via cvs
commands that preserves version history). I did the same for MACHINES.
BTW, you forgot to update the Makefile.in to reference the new location for
all these files. Argh. Okay, for now I'm just going to undelete everything
at the top level and we can move things into docs/ piece-by-piece (hopefully
with some discussion). When we do, hopefully we can do it by manually
moving the files in the /cvs directories on your server so that we don't
lose the version history...
I'm also not sure that README and README.history should be two separate
files (especially since README.history isn't really about nmh's history, as
the name would imply).
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
[EMAIL PROTECTED] | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
