dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60995] New: Account request for libdrm
Date: Sun, 17 Feb 2013 10:54:03 +0000	[thread overview]
Message-ID: <bug-60995-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 891 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=60995

          Priority: medium
            Bug ID: 60995
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Account request for libdrm
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: dh.herrmann@gmail.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: libdrm
           Product: DRI

Created attachment 74973
  --> https://bugs.freedesktop.org/attachment.cgi?id=74973&action=edit
SSH public key

Hi

I'd like to get an fdo account with access to the libdrm repository so I can
continue my work on the drm manpages.

Name: David Herrmann
Email: dh.herrmann@gmail.com
Account: dvdhrm

SSH and GPG public keys are attached.

Thanks
David

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2343 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2013-02-17 10:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-17 10:54 bugzilla-daemon [this message]
2013-02-17 10:55 ` [Bug 60995] Account request for libdrm bugzilla-daemon
2013-03-01  7:11 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-60995-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox