Re: [gentoo-dev] Git Commit Procedures
On Mon, Jul 26, 2010 at 01:46:22PM -0400, Richard Freeman wrote:
> On 07/26/2010 12:32 AM, Jeremy Olexa wrote:
> > On 07/24/2010 10:10 AM, Richard Freeman wrote:
> >
> >> 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.
> >
> > See "Git Repositories" on http://sources.gentoo.org
> >
> > or
> >
> > http://sources.gentoo.org/gitweb/?p=devmanual.git;a=summary
> Would this work for commits? Assuming of course that I had rights to
> commit?
# git clone git+ssh://${devuserna...@git.gentoo.org/var/gitroot/devmanual.git
The /var/gitroot/ part will be dropping later, and the username changing
to 'git', when we use gitolite.
--
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail : robb...@gentoo.org
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
pgpiFVh2yanD9.pgp
Description: PGP signature
Re: [gentoo-dev] Git Commit Procedures
On 07/26/2010 12:32 AM, Jeremy Olexa wrote: On 07/24/2010 10:10 AM, Richard Freeman wrote: 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. See "Git Repositories" on http://sources.gentoo.org or http://sources.gentoo.org/gitweb/?p=devmanual.git;a=summary Would this work for commits? Assuming of course that I had rights to commit? 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. Attach a patch to bug. That repo is not open for anyone to commit to, you have to be a member of the QA team, (or approval from Halcy0n or Betelguese) Makes sense. That would be the issue in this case. My general point was that documentation in general around git is very vague, except for the overlays (which is still lacking, but there is enough info to at least be dangerous there). Maybe a worked example with full command lines might be helpful - starting from scratch check out repository, change a file, and commit it to the official repository. The info out there does require filling in a lot of blanks, and since git itself has no concept of a central repository there aren't a lot of examples of how to do this. Such an example should of course factor in any Gentoo-isms as well (changelogs (if applicable), commit messages, etc - anything we ought to be doing). Rich
Re: [gentoo-dev] Git Commit Procedures
On 07/24/2010 10:10 AM, Richard Freeman wrote: 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. See "Git Repositories" on http://sources.gentoo.org or http://sources.gentoo.org/gitweb/?p=devmanual.git;a=summary 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. Attach a patch to bug. That repo is not open for anyone to commit to, you have to be a member of the QA team, (or approval from Halcy0n or Betelguese) -Jeremy
[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
