public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jon Portnoy <avenj@gentoo.org>
To: Todd Berman <tberman@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ebuild question
Date: Fri, 30 May 2003 10:55:49 -0400	[thread overview]
Message-ID: <20030530145549.GA3690@cerberus.oppresses.us> (raw)
In-Reply-To: <1054305608.19757.3.camel@devweb>

On Fri, May 30, 2003 at 10:40:09AM -0400, Todd Berman wrote:
> Not to generate useless traffic, but I feel it is very important to
> reiterate this.
> 
> Please, please, please attach your ebuilds to bugzilla as text/plain and
> as single files. Two common errors I have seen plenty are attaching a
> .tar.gz or .tar.bz2, or, and more of a problem for me, are the text
> files attached, but set as an octet stream so the viewer wont kick in.
> 
> This cant be stressed enough as the 'proper' way to submit an ebuild if
> you want to see it committed as fast as possible.
> 
> And as an aside, maybe zhen or whoever maintains bugs.g.o can set
> text/plain as the default file upload, because i assume plenty of people
> just forget to change it.
> 
> --Todd
> 
> On Fri, 2003-05-30 at 10:33, Alastair Tse wrote:
> > On Fri, 2003-05-30 at 15:22, MAL wrote:
> > > Is it better to upload an ebuild as a .tar.bz2 with digests, patches 
> > > etc. all included?
> > 
> > Ebuilds should not be attached as tar.bz2, they should be in text/plain.
> > It's actually written in the Ebuils Contribution Guide somewhere, and
> > also one of the most common problems with ebuild submission as I listed
> > in my ebuild mistakes list
> > (http://cvs.gentoo.org/~liquidx/ebuildmistakes.html).
> > 
> > Cheers,
> 
> 

Just to throw in a "me too" - it drives me absolutely nuts when people 
don't submit ebuilds as plain text. Patches et al should also be plain 
text. It's much easier for me to review it that way and will definitely 
get your ebuild processed faster.


-- 
Jon Portnoy
avenj/irc.freenode.net

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-05-30 14:55 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 11:15 [gentoo-dev] ebuild question MAL
2003-05-30 11:29 ` Alastair Tse
2003-05-30 14:22   ` MAL
2003-05-30 14:33     ` Alastair Tse
2003-05-30 14:40       ` Todd Berman
2003-05-30 14:55         ` Jon Portnoy [this message]
2003-05-30 15:08           ` MAL
2003-05-30 14:39     ` Seemant Kulleen
2003-05-30 15:09       ` Seemant Kulleen
  -- strict thread matches above, loose matches on Subject: below --
2005-03-03  3:40 pepone pepone
2005-03-03  3:47 ` Jeremy Hanmer
2005-03-03 10:26   ` Aaron Walker
2005-03-03 20:23     ` Jeremy Hanmer
2005-03-04  0:42       ` Aaron Walker
2003-09-19 14:57 Philippe Lafoucrière
2003-09-19 15:03 ` Georgi Georgiev
2003-09-19 15:12   ` Philippe Lafoucrière
2003-09-19 15:26     ` Georgi Georgiev
2003-09-19 15:05 ` Thomas de Grenier de Latour
2003-09-19 15:15   ` Philippe Lafoucrière
2003-06-10 14:25 MAL
2003-06-12 11:34 ` Amiel Martin
2003-05-30 15:17 William Hubbs
2003-05-30 15:27 ` Grant Goodyear
2003-05-31  3:00   ` Georgi Georgiev
2002-11-26 21:27 Per Wigren
2002-11-26 21:23 ` Dan Armak
2002-11-27  0:03   ` Per Wigren
2002-07-26 14:54 John Matthews
2002-04-18  6:13 Avi Schwartz
2002-04-18  6:59 ` George Shapovalov
2002-04-18  7:15 ` Tod M Neidt
2002-04-17  5:21 Richard Jackson
2002-04-17  5:02 ` Jared H. Hudson
2002-04-17  6:05   ` Richard Jackson
2002-04-17  5:21     ` Jared H. Hudson
2002-02-07  3:44 Edward Muller
2002-02-07  4:43 ` Tod M Neidt
2001-08-05 15:50 Craig Joly
2001-08-05 17:07 ` Daniel Robbins

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=20030530145549.GA3690@cerberus.oppresses.us \
    --to=avenj@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=tberman@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