git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Nicolas Pitre <nico@cam.org>
Subject: Re: [PATCH] Change 'Deltifying objects' to 'Delta compressing objects'
Date: Thu, 18 Oct 2007 22:47:48 -0400	[thread overview]
Message-ID: <20071019024748.GB14735@spearce.org> (raw)
In-Reply-To: <20071019023425.GB8298@coredump.intra.peff.net>

Jeff King <peff@peff.net> wrote:
> On Thu, Oct 18, 2007 at 10:21:54PM -0400, Shawn O. Pearce wrote:
> 
> > My eyes have gotten used to "Deltifying" but I have to admit that
> > in my early Git days I thought it looked damn odd.  Today I'm far
> > too familiar with Git to really notice this as a problem now.
> 
> OK, I will confess I found it a little odd at first, but I think it's a
> straightforward and playful extension of the language, which is
> something I like. But you know, we have the corporate git customers to
> think about these days. ;)

Heh.  Yeah, Git is gaining users on a daily basis.  Its good.  :)
 
> On a similar note, some complaints with progress meters, even after
> recent patches:
> 
>   - When fetching, one progress meter says "Indexing" which, while
>     technically true, is almost certainly blocking on "Downloading". In
>     fact, it is not clear from the existing messages exactly _when_ we
>     are downloading, and when we are just computing, which is something
>     I think a user might want to know. Objections to changing this
>     (though perhaps index-pack will need to be told when it is
>     downloading and when it is just indexing)? Objections to a
>     throughput indicator?

Yes!  I agree entirely.  This is actually not very difficult.

I think the only time we run `git-index-pack --stdin` is from within
git-fetch-pack and git-receive-pack.  These are the only two points
where index-pack's stdin is attached to a network socket and not
to a file.  Its also where you'd want this to say "Transferring",
"Uploading" or "Downloading".

Really the important one to change here is probably the call in
fetch-pack.c as that is the most visible and most time consuming
operation for the average user (think git-clone on a large project).

The same change probably should also be made for unpack-objects as
fetch-pack/receive-pack may have chosen to use that if the object
count is low and it wasn't instructed to keep the packfile.

>   - Running git-gc, we now get something like:
>       Counting objects: 62317, done.
>       Deltifying objects: 100% (18042/18042), done.
>       Writing objects: 100% (62317/62317), done.
>       Total 62317 (delta 43861), reused 61404 (delta 43036)
>       Pack pack-32f8ac40c1a5ec146e45c657cb16f53fdd354095 created.
>       Removing unused objects 100%...
>       Done.
>     Can we get rid of total statistics (I think this is useful for some
>     power users, but perhaps there should be a verbosity level), the
>     name of the pack file (same deal), and the totally useless "Done."?

Yea.  I keep forgetting to write a patch to do this.  I've had much
the same thought as you.

The verbosity should probably be controlled like merge-recursive's
is, but should default to not showing the "Total" line or the "Pack
.. created" line.  For the average user there isn't any valuable
information in either line.

I also think that the progress meter of git-prune-packed should be
fixed to use the standard progress meter system.  And maybe also
be delayed so it doesn't trip if its going to be very quick.

-- 
Shawn.

  reply	other threads:[~2007-10-19  2:48 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  0:45 [PATCH] Change 'Deltifying objects' to 'Delta compressing objects' Shawn O. Pearce
2007-10-19  2:12 ` Jeff King
2007-10-19  2:19   ` Sam Vilain
2007-10-19  2:24     ` David Symonds
2007-10-19  2:34       ` Shawn O. Pearce
2007-10-19  3:02         ` Nicolas Pitre
2007-10-19  2:36       ` Jeff King
2007-10-19  2:55         ` Sam Vilain
2007-10-19  2:25     ` Jeff King
2007-10-19  2:21   ` Shawn O. Pearce
2007-10-19  2:34     ` Jeff King
2007-10-19  2:47       ` Shawn O. Pearce [this message]
2007-10-19  3:01       ` Nicolas Pitre
2007-10-19  3:07         ` Jeff King
2007-10-19  3:24           ` Nicolas Pitre
2007-10-19  3:32             ` Jeff King
2007-10-19  3:50               ` Nicolas Pitre
2007-10-19  3:56                 ` Jeff King
2007-10-19  4:21                   ` Linus Torvalds
2007-10-19  4:29                     ` Jeff King
2007-10-19 11:58                       ` Nicolas Pitre
2007-10-19 19:00                         ` Linus Torvalds
2007-10-19 21:57                           ` Linus Torvalds
2007-10-19  5:09                 ` Shawn O. Pearce
2007-10-19  3:33             ` Shawn O. Pearce
2007-10-19  5:03         ` [PATCH] Stop displaying "Pack pack-$ID created." during git-gc Shawn O. Pearce
2007-10-19  2:49     ` [PATCH] Change 'Deltifying objects' to 'Delta compressing objects' Nicolas Pitre
2007-10-19  3:17       ` Shawn O. Pearce
2007-10-19  3:38         ` Nicolas Pitre
2007-10-19  3:41           ` Jeff King
2007-10-19  3:45           ` Shawn O. Pearce
2007-10-19  4:02             ` Nicolas Pitre
2007-10-19 11:44             ` Wincent Colaiuta
2007-10-19  2:45   ` Nicolas Pitre
2007-10-19  2:59     ` Jeff King
2007-10-19  3:11       ` Nicolas Pitre
2007-10-19  3:15         ` Jeff King
2007-10-19  3:27           ` Nicolas Pitre

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=20071019024748.GB14735@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=peff@peff.net \
    /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).