From: Tomas Carnecky <tom@dbservice.com>
To: Gerhard Wiesinger <lists@wiesinger.com>
Cc: kusmabite@gmail.com, Thomas Rast <trast@student.ethz.ch>,
git@vger.kernel.org
Subject: Re: Global .git directory
Date: Wed, 28 Apr 2010 08:22:10 +0200 [thread overview]
Message-ID: <4BD7D412.5020603@dbservice.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1004280710380.27548@bbs.intern>
On 4/28/10 7:33 AM, Gerhard Wiesinger wrote:
> BTW: The tutorial on http://git-scm.com/ is IHMO wrong:
> git --version
> git version 1.6.2.5
> git commit -m 'Explain what I changed'
> =>
> git commit -a -m 'Explain what I changed'
> => Otherwise changed files are not committed, only added ones.
> => Therefore that are 2 commit ...
If you mean the snippets right on the front page, it assumes that you
add all edited files.
> BTW2:
> Why is it necessary to do:
> # Displays only changed files
> git diff
> # Displays only added files
> git diff --cached
>
> I would like to have a full diff of my changes:
> git diff -a
> (or better "git diff -a" should be the default behaviour, I think that's
> very confusing for new users)
What are 'your' changes? Between HEAD and the working tree (aka. git
diff HEAD)?
tom
next prev parent reply other threads:[~2010-04-28 6:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 5:14 Global .git directory Gerhard Wiesinger
2010-04-27 9:59 ` Thomas Rast
2010-04-27 20:06 ` Gerhard Wiesinger
2010-04-27 20:26 ` Erik Faye-Lund
2010-04-28 5:33 ` Gerhard Wiesinger
2010-04-28 6:22 ` Tomas Carnecky [this message]
2010-04-28 20:03 ` Gerhard Wiesinger
2010-04-28 8:01 ` Alex Riesen
2010-04-28 20:10 ` Gerhard Wiesinger
2010-04-28 12:50 ` Erik Faye-Lund
2010-04-28 20:22 ` Gerhard Wiesinger
2010-05-04 5:07 ` Gerhard Wiesinger
2010-05-04 5:40 ` Andrew Ruder
2010-05-04 6:02 ` Andreas Ericsson
2010-05-04 6:07 ` Gerhard Wiesinger
2010-05-04 16:55 ` Junio C Hamano
2010-04-27 20:37 ` Jacob Helwig
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=4BD7D412.5020603@dbservice.com \
--to=tom@dbservice.com \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
--cc=lists@wiesinger.com \
--cc=trast@student.ethz.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.