[gentoo-dev] Git Commit Procedures
Are the procedures for using git with anything but an overlay on gentoo documented anywhere? I'm trying to make a correction to the devmanual (assuming this is supposed to be general access) for bug 293629. However, I can't seem to find where to clone the repository from. If this isn't supposed to be edited by devs at large, then somebody can feel free to close that bug. It had been open for ages so I figured I might just see if I could take care of it. In general I think that before we can really consider any kind of migration to git we need to actually publish at least a little documentation around how it is to be used. Sure, devs can read the various tutorials online, but what will Gentoo's policy be on putting branches in the official repository, and where should sources be checked out from, and what if anything do devs need to do besides a git push so that everybody doesn't get upset, etc. It need not be 40 pages of documentation, but for something we're already using in an official capacity there should probably be at least a little documentation. It exists for the overlays, although barely (just a bunch of commands without much explanation, and they are commands that would not be covered in any normal git tutorial). Rich
[gentoo-dev] Last Rights: app-misc/gwine
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dead Upstream, last update 2005 Bug 271939 fails with international characters in database Bug 239615 fails to build Masked for removal in 30 days - -- David Abbott (dabbott) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxLOt8ACgkQcZ+z4vAcSsxLMQCggNz4x39bJyRr0FeoZlWnO/H/ 5y0An0kL86H4XFKHtXUpc01M/n6nnWxx =wgtO -END PGP SIGNATURE-
[gentoo-dev] Council Agenda proposal for upcoming 2010-07-26 meeting
Hi, following is the Council Agenda proposal for the upcoming meeting on Monday, July 26th. * allow all members to show up (5 min) ** vote ** add --as-needed to default profile's LDFLAGS ** discuss / vote ** - required-use: http://dev.gentoo.org/~ferringb/required-use.html - review eclass removal policy should it be 2 years since portage 2.1.4.4 went stable? - should there a policy about eclass API changes? - use of invalid DEPEND atom EAPI_TOO_OLD instead of calling die in global scope on eclasses http://archives.gentoo.org/gentoo-dev/msg_dee3aab5e8c840ed3fa4add9c7d74b97.xml and replies - mailing lists should we post council agenda to -council? -dev? -project? some devs suggest we should cross-post to -dev and -council but not everyone likes cross-posting as it can lead to fragmentation Petteri suggested punting -council and using -project instead * go through bugs assigned to coun...@g.o * open floor: listen to developers --- If you have something urgent not included above, please reply to this thread. --- Note that I haven't added a duration to anything but the rollcall. Instead, I recommend we follow a 10 minutes per topic rule. If a topic's discussion passes the 10 minute mark without reaching a decision, we move further discussion to the mailing lists. If we need to vote for that topic, we move it to the next agenda with a *vote* flag. Items with a *vote* flag cannot be moved a second time (unless there's new data to consider), so they must be settled at that agenda's meeting, in an attempt to avoid endless discussions. What do you think? -- Alex Alexander :: wired Gentoo Developer www.linuxized.com pgpOt4l86b35Q.pgp Description: PGP signature
