> 1. http://git-scm.com/book
> 2. http://www.catb.org/esr/faqs/smart-questions.html#beprecise
The classic is
How to Report Bugs Effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
including
"Show me how to show myself."
If you have to report a bug to a programmer who can't be present
in person, the aim of the exercise is to enable them to reproduce
the problem. You want the programmer to run their own copy of the
program, do the same things to it, and make it fail in the same
way. When they can see the problem happening in front of their
eyes, then they can deal with it.
So tell them exactly what you did. If it's a graphical program,
tell them which buttons you pressed and what order you pressed
them in. If it's a program you run by typing a command, show them
precisely what command you typed. Wherever possible, you should
provide a verbatim transcript of the session, showing what
commands you typed and what the computer output in response.
Give the programmer all the input you can think of. If the program
reads from a file, you will probably need to send a copy of the
file. If the program talks to another computer over a network, you
probably can't send a copy of that computer, but you can at least
say what kind of computer it is, and (if you can) what software is
running on it.
Dale
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
