Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Abhijit Halder <abhijit.k.halder@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: How do I create a developer account
Date: Sat, 09 Jul 2011 07:32:00 -0000	[thread overview]
Message-ID: <CAOhZP9z4=LSHa7Oz6qYDM=7V0t1ABnLV-kXha+AyyfNOxy7J3w@mail.gmail.com> (raw)
In-Reply-To: <CAJaTeTriLjddt_UY40s5fXQOMz17CP3oPL9FzX3pka1GCgD5qw@mail.gmail.com>

Hi Mike,

Thanks a lot for your response. I am really excited getting such a
prompt reply. I have couple of doubts.
1. To submit a patch do I need a bug-id?
2. If I am planning to introduce a new feature (enhancement) how to
get a bug-id for that.
3. To create a patch do I need to do a CVS diff (or simple diff
command is sufficient, if then what option should I use). With
anonymous CVS login I could not do a cvs update or cvs diff.

On Sat, Jul 9, 2011 at 12:15 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Sat, Jul 9, 2011 at 02:40, Abhijit Halder wrote:
>> I want to contribute features for gdb. Please let me know how I can
>> create CVS account for code checkin. I am able to checkout code from
>> read-only CVS. For a read/write CVS access I need an account. Please
>> help me regarding this.
>
> you dont need an account to contribute.  anyone can post patches to
> the gdb-patches mailing list and get things merged.
>
> once you've shown significant activity, you'd sign a FSF copyright
> assignment, get an account, and then get approval access.
>
> but unless i've missed something, you havent posted any patches to gdb
> yet.  the process is:
>  - post patches
>  - become known
>  - get account
>  - post more patches
>  - commit things under approval
> not really the other way around
> -mike
>


  reply	other threads:[~2011-07-09  6:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-09  6:46 Abhijit Halder
2011-07-09  6:59 ` Mike Frysinger
2011-07-09  7:32   ` Abhijit Halder [this message]
2011-07-09  7:50     ` Mike Frysinger
2011-07-09  8:30       ` Abhijit Halder

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='CAOhZP9z4=LSHa7Oz6qYDM=7V0t1ABnLV-kXha+AyyfNOxy7J3w@mail.gmail.com' \
    --to=abhijit.k.halder@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.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