Hi,
I've just had a look at http://wiki.debian.org/Games/VCS and I'm a bit
afraid. First off, there are plenty of things listed there, which is a
good thing. But it looks quite messy to me, and even knowing a bit about
those tools, I'm tempted to run away. :)
I'd like to propose the following things:
- Split that page in two pages, e.g. vcs-svn and vcs-git, and link to
those pages instead.
- Have a more logical division between the following parts (maybe in a
different order):
- migration from svn;
- initial import for a new package;
- day to day use.
That said, I've got a couple of comments:
- I'd rather point to ~/.gitconfig than to exporting variables (one
usually puts the exports in ~/.bashrc and forgets about sourcing it,
relogging, etc.; and that's the way to specify those info anyway).
Note that it can be overriden with a local .git/config in any git
repository.
- Use “git *” rather than “git-*” in documentation, since the former is
planned for removal. The usage doesn't change at all, but I think
it's better to be prepared to use the new form, and now that the
documentation will still be available as “man git-*”.
- I fear that git pull will create dummy merge entries, I'd rather
advocate the use of git fetch, and then git merge or git rebase
depending on the appropriate use. I've got to check vcs-pkg.org,
there might be nice (possibly graphical) explanations about that.
That's all for now. Oh, and I didn't forget what I wrote an hour ago,
but I quite sure it's not worth pasting the current page right now, it'd
be better to have it splitted into smaller parts before discussing it
more in depth.
Mraw,
KiBi.
Attachment:
pgpf6DI069RrQ.pgp
Description: PGP signature