Re: more than 20 commands in everyday.txt
Miklos Vajna <vmiklos@frugalware.org> writes:
Show 10 quoted lines
> 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?
I agree that git-repack should be removed (there is git-gc), and git-prune should be replaced by mentioning --prune option to git-gc. This document is for newbies, and they shouldn't need to run anything other than git-gc.
Besides with new enough git the number of generated loose objects
should be greatly reduced: git now produces (small) packs if
possible.
I'm not sure if mentioning git-fsck at all, or at least this early is
a good idea for introductory tutorial. Running git-fsck should be
rare, very rare.
> - git-show-branch: what about mentioning gitk instead? i think it's much
> more used - compared to git-show-branch
I would replace git-show-branch by git-show as command to see where you are. and add gitk (which has now manpage) to view history. git-show-branch output is a bit cryptic...
Perhaps we could add git-reflog / "git log -g" somewhere around?
> 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'd like this. At least the first one is unambiguous.
--
Jakub Narebski
Poland
ShadeHawk on #git
Miklos Vajna
