[m-rev.] [reuse] synchronize reuse branch with main branch
Nancy Mazur
Nancy.Mazur at cs.kuleuven.ac.be
Wed Sep 11 17:03:14 AEST 2002
* Fergus Henderson <fjh at cs.mu.OZ.AU> [2002-09-10 20:01]:
> On 10-Sep-2002, Nancy Mazur <Nancy.Mazur at cs.kuleuven.ac.be> wrote:
> >
> > Well, I was planning to commit it, but I obtain an endless series of
> > errors concerning the absence of non-uptodatedness of the copyright
> > message, especially in directories such as boehm_gc, etc...
> >
> > What do I do with these? I thought that's wat the .nocopyright file is
> > for? What is the standard procedure?
>
> For code which is imported another source, e.g. just about everything
> in the boehm_gc directory except the Mmakefile, just add the relevant
> files to the .nocopyright file in that directory.
1. comparing the .nocopyright file with the .nocopyright-file from my
main-branch yields the result: they are the same. Nevertheless, I have
problems with the files. (I'd think it should give no errors of that
kind, as I haven't added new files... ).
2. I've added one specific file (BCC_MAKEFILE) to .nocopyright,
committed the .nocopyright file, and then tried to commit BCC_MAKEFILE.
It still complains about a missing copyright.
What seems strange to me is that BCC_MAKEFILE should be in the
main-branch .nocopyright file already? or not? Idem for a number of
other files in that directory...
> For code whose master repository is our repository, update the copyright
> message.
>
> For files whose master repository is our repository, but which are not code
> (e.g. README files), it's usually OK to omit the copyright message,
> i.e. just add them to the .nocopyright file.
Nancy
--------------------------------------------------------------------------
mercury-reviews mailing list
post: mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------
More information about the reviews
mailing list