All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: jon@blackcubes.dyndns.org
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Core and Not-So Core
Date: Tue, 10 May 2005 18:03:29 +0100	[thread overview]
Message-ID: <1115744609.16187.455.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <2cfc4032050510092238259b63@mail.gmail.com>

On Wed, 2005-05-11 at 02:22 +1000, Jon Seymour wrote:
> So, no, it's not a religious issue. If anything, it is being dogmatic
> to insist that the sacred GIT repository structure only be manipulated
> by 'C' tools blessed by the hands of Linus.

Given the volatility of the structure -- at least the details if not the
fundamentals -- it seems bizarre to want to reimplement it rather than
just using the existing tools.

This is the same mentality which gives Eclipse a half-arsed SSH
reimplementation which doesn't behave like normal SSH is configured to
behave either, right?

-- 
dwmw2


  reply	other threads:[~2005-05-10 16:56 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-10 15:00 Core and Not-So Core Jon Seymour
2005-05-10 15:38 ` David Woodhouse
2005-05-10 15:50   ` Eduardo Teixeira Dias
2005-05-10 16:00     ` David Woodhouse
2005-05-10 16:19       ` Eduardo Teixeira Dias
2005-05-10 21:45         ` Diego Calleja
2005-05-10 22:33           ` Eduardo Teixeira Dias
2005-05-10 23:03             ` Diego Calleja
2005-05-10 23:11               ` Horst von Brand
2005-05-10 22:33           ` Eduardo Teixeira Dias
2005-05-10 22:34           ` Eduardo Teixeira Dias
2005-05-10 22:44           ` Petr Baudis
2005-05-10 22:54             ` Andreas Gal
2005-05-10 23:04             ` James Purser
2005-05-11  7:17           ` Christoph Hellwig
2005-05-11  7:42             ` Jon Seymour
2005-05-10 16:22   ` Jon Seymour
2005-05-10 17:03     ` David Woodhouse [this message]
     [not found]       ` <2cfc403205051010151304d88a@mail.gmail.com>
2005-05-10 17:15         ` Jon Seymour
2005-05-10 17:25           ` David Woodhouse
2005-05-10 17:36             ` Jon Seymour
2005-05-10 17:41               ` Christoph Hellwig
     [not found]                 ` <2cfc40320505101051207c9ce4@mail.gmail.com>
2005-05-10 17:51                   ` Jon Seymour
2005-05-10 18:01                     ` Davide Libenzi
2005-05-11  1:59           ` Rik van Riel
2005-05-11  2:09             ` Jon Seymour
2005-05-11  2:14               ` Petr Baudis
2005-05-10 22:18 ` Daniel Barkalow
     [not found]   ` <2cfc40320505101605721420@mail.gmail.com>
2005-05-10 23:05     ` Jon Seymour
2005-05-10 23:08       ` Petr Baudis
2005-05-10 23:20         ` Jon Seymour
2005-05-11 16:45           ` Daniel Barkalow
     [not found]             ` <2cfc403205051114087d283279@mail.gmail.com>
2005-05-11 21:09               ` Jon Seymour
2005-05-10 22:52 ` Petr Baudis
2005-05-11  0:50   ` Jon Seymour
2005-05-11  1:17     ` Peter Williams
2005-05-11  2:30     ` Nicolas Pitre
2005-05-11  3:02       ` Jon Seymour
2005-05-11 11:21 ` Noel Grandin
2005-05-11 14:40   ` Jon Seymour
2005-05-18 18:35 ` Juliusz Chroboczek

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=1115744609.16187.455.camel@hades.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=git@vger.kernel.org \
    --cc=jon@blackcubes.dyndns.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.