Re: Reenabled account for Tomasz Kloczko
- From: Owen Taylor <otaylor redhat com>
- To: seth eazel com
- Cc: Tomasz Kłoczko <kloczek rudy mif pg gda pl>, gnome-private gnome org, gnome-hackers gnome org, kloczek pld org pl
- Subject: Re: Reenabled account for Tomasz Kloczko
- Date: 12 Mar 2001 12:33:27 -0500
Seth Nickell <snickell stanford edu> writes:
> > I think maybe some partial solution for prevent on not technical level
> > cases like mine can be prepare document in each module with rule (for
> > peoples not listed for example in module AUTHORS files) for consult on
> > proper list or with maintainer each change. IMHO try promote make good
>
> Augh! For people who don't already know (everyone with commit access
> should), the file is called HACKING. Almost every (every?) module in the
> GNOME CVS tree has such a file, and it tells you the rules for
> committing etc. Often it will specify a mailing list to submit patches
> to for approval. What we really should have is a thorough document
> everyone has to read before they get a CVS account!
Actually, this came up in the earlier discussion and the name of the
file telling you the rules for CVS commits is traditionally called:
README.cvs-commits.
HACKING is supposed to tell you what all you need to do to get the
module building out of CVS.
Regards,
Owen
_______________________________________________
gnome-hackers mailing list
gnome-hackers gnome org
http://mail.gnome.org/mailman/listinfo/gnome-hackers
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]