From: "Kevin D. Kissell" <kevink@mips.com>
To: Florian DELIZY <florian.delizy@sagem.com>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>, linux-mips@linux-mips.org
Subject: Re: Réf. : Re: linux-mips Vs kernel.org
Date: Tue, 27 Sep 2005 11:18:38 +0200 [thread overview]
Message-ID: <43390E6E.7030703@mips.com> (raw)
In-Reply-To: <OF09624E56.0EE9A8E5-ONC1257089.0031D0AF-C1257089.00320CF1@sagem.com>
Florian DELIZY wrote:
> Is that meaning that kernel.org source code is merged into linux-mips.org
> repository,
> or that linux-mips.org code is merged into the kernel.org source
> repository ?
Les deux. But kernel.org -> linux-mips.org merges are more frequent.
Regards,
Kevin K.
prev parent reply other threads:[~2005-09-27 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 9:06 Réf. : Re: linux-mips Vs kernel.org Florian DELIZY
2005-09-27 9:11 ` Jan-Benedict Glaw
2005-09-27 9:18 ` Kevin D. Kissell [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=43390E6E.7030703@mips.com \
--to=kevink@mips.com \
--cc=florian.delizy@sagem.com \
--cc=jbglaw@lug-owl.de \
--cc=linux-mips@linux-mips.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