From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Michal Simek <simekm2@fel.cvut.cz>,
linux-kernel@vger.kernel.org, monstr@monstr.eu
Subject: Re: New linux arch
Date: Mon, 07 Jan 2008 18:26:33 +0100 [thread overview]
Message-ID: <478260C9.6040407@s5r6.in-berlin.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0801071433510.14194@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
>>On Jan 7, 2008 1:29 PM, Michal Simek <simekm2@fel.cvut.cz> wrote:
>>> Is it possible to create git repository in git.kernel.org for Microblaze
>>> cpu?
...
> Alternatively, providing your own git service is just as effective,
> and comes with much more freedom :)
It is /almost/ as effective:
- Many of the git trees on kernel.org are set up to share objects with
Linus' tree.
- The tree owners can fetch from each other locally and via ssh:
protocol, alternatively to the remote protocols.
But it is exactly as effective in terms of the workflow organization.
--
Stefan Richter
-=====-==--- ---= --===
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-01-07 17:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 11:29 New linux arch Michal Simek
2008-01-07 12:34 ` Sam Ravnborg
2008-01-07 12:51 ` Michal Simek
2008-01-07 19:16 ` Sam Ravnborg
2008-01-07 12:47 ` Pekka Enberg
2008-01-07 13:00 ` Michal Simek
2008-01-07 13:12 ` Pekka Enberg
2008-01-07 13:34 ` Jan Engelhardt
2008-01-07 17:26 ` Stefan Richter [this message]
2008-01-07 17:39 ` Jan Engelhardt
2008-01-07 17:54 ` H. Peter Anvin
2008-01-07 18:20 ` Stefan Richter
2008-01-07 22:00 ` Benjamin Herrenschmidt
2008-01-07 22:39 ` Michal Simek
2008-01-08 8:28 ` Bryan Wu
2008-01-08 8:49 ` Pekka Enberg
2008-01-08 9:00 ` Bryan Wu
2008-01-08 17:05 ` Stefan Richter
2008-01-08 17:12 ` Stefan Richter
2008-01-09 1:16 ` Arnd Bergmann
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=478260C9.6040407@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=penberg@cs.helsinki.fi \
--cc=simekm2@fel.cvut.cz \
/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