All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jonas Juselius" <jonas.juselius@chem.uit.no>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: <git@vger.kernel.org>
Subject: Re: Git in a Nutshell guide
Date: Mon, 19 Nov 2007 17:14:37 +0100	[thread overview]
Message-ID: <1195488877.10573.29.camel@localhost> (raw)
In-Reply-To: <fhsc7b$k4g$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

On Mon, 2007-11-19 at 17:05 +0100, Jakub Narebski wrote:
> By the way, the description of this repository (for gitweb) is
> "CVS to git migration guide", the same as for CVS2git.git
> (shouldn't it be CVS2git_guide.git?).

Well, it's the same repository. When I started out, I only planned to
write the CVS2git manual. Then I wrote the Nutshell guide, and changed
the name of the repo, but I had already given the link to a bunch of
people so I kept the link.

> 
> Perhaps you should have make gitweb.cgi with 
>   GITWEB_BASE_URL="http://git.jonas.iki.fi"
> then, or configure @git_base_url_list in gitweb_config.perl.
> 

I'll look into that :)

> Do I understand correctly that you don't support cloning via git://
> protocol?

Yes, that is correct. The machine is behind a number of firewalls, and I
simply cannot be bothered to go through the bureaucracy...

.j.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-11-19 16:14 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 13:05 Git in a Nutshell guide Jonas Juselius
2007-11-19 13:29 ` Jakub Narebski
2007-11-19 14:33   ` Jonas Juselius
2007-11-22  8:22   ` David Kågedal
2007-11-23  9:28     ` Jakub Narebski
2007-11-19 15:02 ` Brian Downing
2007-11-19 15:03   ` Brian Downing
2007-11-19 15:48   ` Nicolas Pitre
2007-11-19 16:05 ` Jakub Narebski
2007-11-19 16:14   ` Jonas Juselius [this message]
2007-11-19 16:49     ` Benoit Sigoure
2007-11-19 22:01       ` Daniel Barkalow
2007-11-20 11:34       ` Jonas Juselius
2007-11-20 23:57       ` Jakub Narebski
2007-11-21 19:45         ` Jan Hudec
2007-11-21 21:32           ` Jakub Narebski
2007-11-22 16:37             ` jhud7196
2007-11-22 13:15   ` Jonas Juselius
2007-11-22 14:19     ` Jonathan del Strother
2007-11-22 14:24     ` Johannes Schindelin
2007-11-22 16:57     ` jhud7196
2007-11-19 16:45 ` Lars Hjemli
2007-11-19 16:56   ` Jonas Juselius
2007-11-19 16:57   ` Benoit Sigoure
2007-11-19 17:04     ` Lars Hjemli
2007-11-19 18:10       ` Benoit Sigoure
2007-11-19 18:13         ` J. Bruce Fields
2007-11-19 18:13         ` Matthieu Moy
2007-11-19 18:35           ` [PATCH] Doc fix for git-reflog: mention @{...} syntax, and <ref> in synopsys Matthieu Moy
2007-11-19 20:13             ` Junio C Hamano
2007-11-19 20:28               ` Matthieu Moy
2007-11-19 20:31                 ` Matthieu Moy
2007-11-19 21:15           ` Git in a Nutshell guide Benoit Sigoure
2007-11-19 21:33             ` Matthieu Moy
2007-11-19 21:51               ` Benoit Sigoure
2007-11-19 22:23                 ` J. Bruce Fields
2007-11-19 22:29                 ` Junio C Hamano
2007-11-19 22:59                   ` Matthieu Moy
2007-11-19 23:07                     ` Junio C Hamano
2007-11-19 17:05     ` Matthieu Moy

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=1195488877.10573.29.camel@localhost \
    --to=jonas.juselius@chem.uit.no \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /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.