All of lore.kernel.org
 help / color / mirror / Atom feed
From: bdowning@lavos.net (Brian Downing)
To: Jonas Juselius <jonas.juselius@chem.uit.no>
Cc: git@vger.kernel.org
Subject: Re: Git in a Nutshell guide
Date: Mon, 19 Nov 2007 09:02:09 -0600	[thread overview]
Message-ID: <20071119150209.GF6212@lavos.net> (raw)
In-Reply-To: <1195477504.8093.15.camel@localhost>

On Mon, Nov 19, 2007 at 02:05:04PM +0100, Jonas Juselius wrote:
> I have also written a CVS2git transition guide, which outlines one
> possible way of converting from CVS to git.

You write:

> In order to save space you can also enable compression
> $ git config --global core.compression 1
> $ git config --global core.loosecompression 1

I think this contradicts the git-config manpage:

>  core.compression
>      An integer -1..9, indicating a default compression level. -1 is the
>      zlib default. 0 means no compression, and 1..9 are various
>      speed/size tradeoffs, 9 being slowest.

>  core.loosecompression
>      An integer -1..9, indicating the compression level for objects that
>      are not in a pack file. -1 is the zlib default. 0 means no
>      compression, and 1..9 are various speed/size tradeoffs, 9 being
>      slowest. If not set, defaults to core.compression. If that is not
>      set, defaults to 0 (best speed).

The default, -1, is the zlib default, which is probably something like 3-6.
Setting these to 1 will probably result in less compression, not more.

-bcd

  parent reply	other threads:[~2007-11-19 15:02 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 [this message]
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
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=20071119150209.GF6212@lavos.net \
    --to=bdowning@lavos.net \
    --cc=git@vger.kernel.org \
    --cc=jonas.juselius@chem.uit.no \
    /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.