public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Robin H.Johnson <robbat2@gentoo.org>
To: Anthony de Boer <adb@leftmind.net>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Ebuilds not getting in :(
Date: Fri, 25 Apr 2003 14:59:31 -0700	[thread overview]
Message-ID: <20030425215931.GB15299@cherenkov.orbis-terrarum.net> (raw)
In-Reply-To: <20030425134659.I30851@leftmind.net>

[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]

On Fri, Apr 25, 2003 at 01:46:59PM -0400, Anthony de Boer wrote:
> You wrote:
> > The since most discougaging thing in any submitted ebuild is the lack of
> > an included ChangeLog. To anybody submitting an ebuild, use
> > skel.ChangeLog, and fill it out with the correct information.
> The skel file says:
> 
>   DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2 :
>   Initial import.  Ebuild submitted by submitter_name <submitter_email>.
> 
> which to me implied that the developer doing the CVS commit puts his/her
> name and address in the first spot.  As the submitter who would be named
> on the second line, how would I phrase the initial ChangeLog?
The submitted changelogs that are nice just have 'INSERT_NAME' for the
developers name+address. But most developers aren't too fussed about the
name+address in the first line.

So if you were submitted it
it might be:

  25 Apr 2003; INSERT_NAME foo-0.0.1.ebuild, files/somepatch:
  Initial import. Ebuild submitted by Anthony de Boer <adb@leftmind.net>
  Other comments go here if needed about the build.

That way I just copy the ChangeLog in, change my name and I'm done.
This may make me seem very lazy, but by including a good changelog like
this in your submission, your package is more likely to get in even just
because it looks complete and you seem to have done your homework ;-).

-- 
Robin Hugh Johnson
E-Mail     : robbat2@orbis-terrarum.net
Home Page  : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ#       : 30269588 or 41961639
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2003-04-25 21:59 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22  7:38 [gentoo-dev] Ebuilds not getting in :( Klavs Klavsen
2003-04-22 12:59 ` Frantz Dhin
2003-04-22 13:09   ` Ragnar Hojland Espinosa
2003-04-22 13:17   ` Peter Ruskin
2003-04-22 13:24     ` FRLinux
2003-04-22 13:30       ` Klavs Klavsen
2003-04-22 13:50     ` Ragnar Hojland Espinosa
2003-04-22 14:05       ` Jon Portnoy
2003-04-22 16:18     ` Brad Laue
2003-04-23 15:25     ` Peter Ruskin
2003-04-23 18:18       ` Paul de Vrieze
2003-04-22 14:26   ` Dan Armak
2003-04-22 14:57     ` Peter Ruskin
2003-04-22 15:40       ` Tony Clark
2003-04-22 15:45         ` Ragnar Hojland Espinosa
2003-04-22 16:00       ` Klavs Klavsen
2003-04-22 16:14         ` Tony Clark
2003-04-22 16:23           ` William Hubbs
2003-04-22 16:59         ` Jon Portnoy
2003-04-22 17:55           ` Mark Bainter
2003-04-22 18:00             ` Klavs Klavsen
2003-04-22 18:06               ` Jon Portnoy
2003-04-25 16:58     ` Brad Laue
2003-04-25 17:31       ` foser
2003-04-25 21:03         ` Brad Laue
2003-04-26  0:38           ` foser
2003-04-22 19:11   ` Fredrik Jagenheim
2003-04-22 23:53     ` Fernand Albarracin
2003-04-22 15:57 ` Brian Jackson
2003-04-22 22:07   ` Brian Jackson
2003-04-22 22:36     ` Robin H.Johnson
2003-04-23  7:43       ` Mark Gordon
2003-04-23 12:46         ` Jon Portnoy
     [not found]       ` <20030425134659.I30851@leftmind.net>
2003-04-25 21:59         ` Robin H.Johnson [this message]
2003-04-23  2:56     ` Brian Jackson
2003-04-23 15:27       ` Peter Fein
2003-04-23 15:38         ` Grant Goodyear
2003-04-24 18:20       ` Brian Jackson
2003-04-23  5:47   ` Thomas Arnhold
  -- strict thread matches above, loose matches on Subject: below --
2003-04-24  0:32 Stroller
2003-04-24  3:50 ` George Shapovalov
2003-04-25  1:01 Stroller

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=20030425215931.GB15299@cherenkov.orbis-terrarum.net \
    --to=robbat2@gentoo.org \
    --cc=adb@leftmind.net \
    --cc=gentoo-dev@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