From: Terje Kvernes <terjekv@math.uio.no>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ebuild policy questions.
Date: 12 Apr 2002 22:10:08 +0200 [thread overview]
Message-ID: <wxxwuvcr84f.fsf@nommo.uio.no> (raw)
In-Reply-To: <1018633472.10970.0.camel@silica.localmosci>
"Tod M. Neidt" <tod@gentoo.org> writes:
> Hi Terje!
hi Tod. :)
> I should have explicitly discussed the distinction between upstream
> and third-party patches and those that are specific to Gentoo Linux.
> I assumed that we were talking about the former in my previous post.
I didn't think much of the difference to be honest. but thanks for
clearing it up.
> Normally gentoo specific patches created by the ebuild author are
> kept in the files directory. A suffix of "-gentoo" is typically
> appended to indicate this. For example,
> xgammon-0.98-gentoo-makefile.patch, or something to that effect.
oki. I'll keep that in mind when writing patches.
> Sorry for any confusion that this may have caused.
stop being sorry for helping. ;)
--
Terje
prev parent reply other threads:[~2002-04-12 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 20:30 [gentoo-dev] ebuild policy questions Terje Kvernes
2002-04-11 21:54 ` Tod M. Neidt
2002-04-12 10:27 ` Terje Kvernes
2002-04-12 17:44 ` Tod M. Neidt
2002-04-12 20:10 ` Terje Kvernes [this message]
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=wxxwuvcr84f.fsf@nommo.uio.no \
--to=terjekv@math.uio.no \
--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