From: Aniruddha <mailing_list@orange.nl>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] What is the preferred way to submit patches?
Date: Sun, 21 Sep 2008 19:32:22 +0200 [thread overview]
Message-ID: <1222018342.21292.0.camel@debian> (raw)
In-Reply-To: <48CEBC3D.9090204@gentoo.org>
On Mon, 2008-09-15 at 12:49 -0700, Josh Saddler wrote:
> Aniruddha wrote:
> > I would like to provide some patches for the Gentoo documentation. What
> > is the best way to do this? I can imagine it's something like:
> >
> > 1 Download xml
> > 2 Adjust
> > 3 Create patch
> > 4 Upload to bugzilla
> >
> > Is this the correct way? And if so what is the best way to download the
> > xml? Which url should I use?
>
> http://www.gentoo.org/proj/en/gdp/doc/doc-tipsntricks.xml#doc_chap4
>
> http://www.gentoo.org/doc/en/xml-guide.xml
>
> Append ?passthru=1 to a .xml URL to see the source.
>
Thanks!
next prev parent reply other threads:[~2008-09-21 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 19:24 [gentoo-doc] What is the preferred way to submit patches? Aniruddha
2008-09-15 19:49 ` Josh Saddler
2008-09-21 17:32 ` Aniruddha [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-15 20:17 Aniruddha
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=1222018342.21292.0.camel@debian \
--to=mailing_list@orange.nl \
--cc=gentoo-doc@lists.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