[cairo-bugs] [Bug 10411] personal public git repo request

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=10411





------- Comment #1 from cworth at cworth.org  2007-03-26 08:38 PST -------
(In reply to comment #0)
> So far as I can tell carl, your message here
> http://lists.freedesktop.org/archives/cairo/2006-February/006335.html
> 
> has the only instructions for requesting a per-user repo. So - can I have one
> please?

Of course you may!

Now, a couple of things have changed since I wrote that email, (and I should
probably write up a new one). Of relevance here is that we no longer encourage
personal repositories on git.freedesktop.org which is locked down, (requiring
someone like me to create/maintain the repositories), but instead on
people.freedesktop.org, (where anyone can create/maintain their own).

So, Brian, do you have a freedesktop.org account yet? If not, I'd be glad to
create one. All you need to do is to let us know your preferred username,
preferred email address and provide a gpg and an ssh key. More instructions are
here:

http://freedesktop.org/wiki/AccountRequests

(And you can just post things to this existing bug report---no need to make any
new report.)

Once you've got an account, (or tell me your username if you've got one
already), then you can create your own repository, or I can help you with it.

-Carl


------- Comment #2 from Brian.Ewins at gmail.com  2007-04-02 12:54 PST -------
That's odd... I didn't get mailed your reply, apparently. 

Yes, I have an account, thanks: brianewins . You added me in bug 9476 :) My
keys are still attached over there.

So, should I be trying to follow something like 
http://wiki.u32.net/index.php?title=Git/publishing
and scp a repo to my account? I've been leaning on git-push too long, I guess,
time to learn a more distributed workflow - pointers appreciated.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.