git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: git@vger.kernel.org
Subject: Re: more than 20 commands in everyday.txt
Date: Wed, 19 Dec 2007 16:15:42 -0800	[thread overview]
Message-ID: <7vejdite4x.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20071219225618.GA7378@genesis.frugalware.org> (Miklos Vajna's message of "Wed, 19 Dec 2007 23:56:18 +0100")

Miklos Vajna <vmiklos@frugalware.org> writes:

> "every day". of course it may be only me, that's why i ask. here are the
> commands i rarely use and are in everyday.txt:
>
> - git-prune and git-repack: usually i use git-gc only. maybe prune and
>   repack could be removed from everyday.txt?
>
> - git-show-branch: what about mentioning gitk instead? i think it's much
>   more used - compared to git-show-branch
>
> what do you think about this? maybe i'm wrong, but if i'm right, then i
> would provide a patch to update everyday.txt according to these
> suggestions.

I think you would probably get unanimous yes for the former (I don't use
gc myself but "repack -a -d" or "repack -a -d -f" regularly, though ---
I am old fashioned and do not mind being counted as an oddball).

For the latter it all depends on whether you are in windowed environment
(I usually don't).

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 22:56 more than 20 commands in everyday.txt Miklos Vajna
2007-12-19 23:23 ` Jakub Narebski
2007-12-20  0:15 ` Junio C Hamano [this message]
2007-12-20 14:05 ` [PATCH] everyday: replace 'prune' with 'gc --prune' Miklos Vajna
2007-12-20 14:05 ` [PATCH] everyday: replace 'repack' with 'gc' Miklos Vajna

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=7vejdite4x.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=vmiklos@frugalware.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).