git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Git Mailing List <git@vger.kernel.org>,
	Martin Langhoff <martin@catalyst.net.nz>,
	Jon Seymour <jon.seymour@gmail.com>
Subject: Re: git-daemon --inetd
Date: Fri, 16 Sep 2005 09:44:13 +1200	[thread overview]
Message-ID: <46a038f905091514447e13404d@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0509151225410.26803@g5.osdl.org>

On 9/16/05, Linus Torvalds <torvalds@osdl.org> wrote:
> Btw, I think --merge-order was cool, but its weaker cousin --topo-order is
> what is actually _used_. Maybe we should deprecate --merge-order? Right
> now the only real user is git-archimport, and I think that one too really
> only wants topo-order too. For example, right now I think git-archimport
> won't actually work if you build without openssl.
> 
> Jon? Martin?

I've used merge-order because it made sense... in that it gave me the
same history and order that walking the arch history would. Most of
the time, anyway, and decided that I'd rather trust GIT over Arch on
merging strategies...

If topo-order is sane, then I'll just change that. Let me run a couple
of tests with it first ;)

WRT SSL... archimport doesn't care a bit about SSL, and if it does,
it's a bug. It calls tla to perform all the "fetch stuff from the Arch
repo operations", because I was too lazy to implement native support
for reading the (trivial) repo format over all the transports. And
with Arch, access to the remote repos is _fast_ (unlike cvs).

cheers,



martin

  reply	other threads:[~2005-09-15 21:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15  6:04 git-daemon --inetd H. Peter Anvin
2005-09-15 16:03 ` Linus Torvalds
2005-09-15 18:30   ` H. Peter Anvin
2005-09-15 18:47     ` Linus Torvalds
2005-09-15 19:19       ` H. Peter Anvin
2005-09-15 19:40         ` Linus Torvalds
2005-09-15 21:44           ` Martin Langhoff [this message]
2005-10-22 13:45             ` Jon Seymour
2005-10-22 21:05               ` Linus Torvalds
2005-09-15 19:57         ` Junio C Hamano
2005-09-16  6:23     ` Junio C Hamano
2005-09-16  7:51   ` Junio C Hamano
2005-09-16 16:54     ` H. Peter Anvin
2005-09-16 17:30     ` Linus Torvalds
2005-09-16 18:23       ` H. Peter Anvin

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=46a038f905091514447e13404d@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=hpa@zytor.com \
    --cc=jon.seymour@gmail.com \
    --cc=martin@catalyst.net.nz \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).