From: Miklos Vajna <vmiklos@frugalware.org>
To: git@vger.kernel.org
Subject: more than 20 commands in everyday.txt
Date: Wed, 19 Dec 2007 23:56:18 +0100 [thread overview]
Message-ID: <20071219225618.GA7378@genesis.frugalware.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
hi,
this might seem to be a bit bikesheding, but i hope it isn't. today i
teched git to someone who never used any scm so far. i showed him the
"everyday with git" document, as i think it's a great start for newbies.
actually i read it once but it was in the past, now i did it again and i
think there are some commands listed there which is not something we use
"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.
thanks,
- VMiklos
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-12-19 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 22:56 Miklos Vajna [this message]
2007-12-19 23:23 ` more than 20 commands in everyday.txt Jakub Narebski
2007-12-20 0:15 ` Junio C Hamano
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=20071219225618.GA7378@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--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 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).