httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <>
Subject Re: cvs commit: apachen STATUS
Date Thu, 08 Jan 1998 17:15:43 GMT
Rodent of Unusual Size wrote:
> Jim Jagielski wrote:
> > 
> > Well, the naming stuff can be flexible IMO with no real guidelines.
> I think there have to be *some* sort of guidelines - remember that
> CVS is going to get gritchy if you give a file the same name as
> one in the attic.  Even it's only a three-digit prefix (such as
> "021-dean_sounds_off_on_syscalls.patch") that's enough for me -
> as long as the guideline is that the number is monotonically
> increasing.

D'oh! Yep... Maybe the # could be the extension (use_assembler.012)

> > Also, a nice thing, is that a nice long explanation can be
> > added to the diffs assuming that one's patch works correctly
> > and ignores them.
> I don't think I understand this paragraph..  do you mean comments
> in the patch file but not within the actual diffs?

Yes... Since patch will ignore "junk" it sees at the top of
patchfiles, each patchfile could also be self-documenting :/

      Jim Jagielski            |       jaguNET Access Services           |
            "Look at me! I'm wearing a cardboard belt!"

View raw message