All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Deprecate git-fetch-pack?
Date: Mon, 12 Nov 2007 01:16:13 +0100	[thread overview]
Message-ID: <fh8609$umn$1@ger.gmane.org> (raw)
In-Reply-To: 20071111235819.GB7392@thunk.org

Theodore Tso wrote:

> 2) The command which are displayed by "git help" should use some
> serious rethinking.  Ideally, it would be nice if the output fit in a
> single 24-line terminal window.   Some candidates for removal:
> 
>        a) prune: "git prune" definitely doesn't deserve to be on the
>        front and center as displayed by "git help".  Maybe replace it
>        with "gc", but now that we have gc.auto, I'm not sure it's
>        worth it at all.

I would replace it by "git gc" (you have to run 'git gc --prune' by hand
on quiescent repository), or remove it altogether.

>        b) revert:  Is that really that common of a command?

It is useful command, perhaps short description should be improved.
BTW. if we have cherry-pick, then we should have revert.

>        c) show-branch: The output is terrifying without explanation

I agree. I would replace it by gitk, or gui (git-gui / "git gui").

> There are other commands I'm not so sure about, but it is worth
> flagging them.  One way that might be helpful is to group the commands
> into subcommands, much like gdb does, so you could do something like
> "git help other-repos" (where all commands that involve interacting
> with other repositories are summarized), and so on.

I think that "git-rm" could be removed, because "rm <file>; git commit ..."
works just fine.

See also discussion about results of Git User's Survey 2007, somewhere
around
  http://thread.gmane.org/gmane.comp.version-control.git/59935/focus=62205

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  reply	other threads:[~2007-11-12  0:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-10 23:11 Deprecate git-fetch-pack? Daniel Barkalow
2007-11-11  0:48 ` Junio C Hamano
2007-11-11  3:09   ` Ask Bjørn Hansen
2007-11-11 11:05     ` Johannes Schindelin
2007-11-11 21:16       ` Junio C Hamano
2007-11-11 22:21         ` Theodore Tso
2007-11-11 22:35           ` Junio C Hamano
2007-11-11 22:50             ` Johannes Schindelin
2007-11-11 23:58               ` Theodore Tso
2007-11-12  0:16                 ` Jakub Narebski [this message]
2007-11-12 17:29                   ` Jon Loeliger
2007-11-12 17:33                     ` Johannes Schindelin
2007-11-12 18:56                       ` Jon Loeliger
2007-11-12 19:08                         ` Johannes Schindelin
2007-11-12 19:16                           ` Jon Loeliger
2007-11-12  0:57                 ` [PATCH,RFC 1/2] Make the list of common commands more exclusive Theodore Ts'o
2007-11-12  0:57                   ` [PATCH,RFC 2/2] Remove hint to use "git help -a" Theodore Ts'o
2007-11-12  2:21                   ` [PATCH,RFC 1/2] Make the list of common commands more exclusive Junio C Hamano
2007-11-12  5:48                     ` Ping Yin
2007-11-12  6:22                     ` Theodore Tso
2007-11-12  7:26                       ` Junio C Hamano
2007-11-12 10:24                         ` Mike Hommey
2007-11-12 12:23                           ` Johannes Schindelin
2007-11-12  7:57                       ` Ask Bjørn Hansen
2007-11-12 10:21                       ` Andreas Ericsson
2007-11-12 15:20                         ` Theodore Tso
2007-11-12 10:15                 ` Deprecate git-fetch-pack? Andreas Ericsson
2007-11-12  1:10               ` Ask Bjørn Hansen
2007-11-11  8:32   ` Mike Hommey

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='fh8609$umn$1@ger.gmane.org' \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.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.