git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Michael S. Tsirkin" <mst@dev.mellanox.co.il>, git@vger.kernel.org
Subject: Re: most commonly used git commands?
Date: Thu, 28 Jun 2007 14:17:32 +1200	[thread overview]
Message-ID: <46a038f90706271917j7abb4bddu21debafe3461c695@mail.gmail.com> (raw)
In-Reply-To: <7vodj41nm6.fsf@assigned-by-dhcp.pobox.com>

On 6/25/07, Junio C Hamano <gitster@pobox.com> wrote:
> "Michael S. Tsirkin" <mst@dev.mellanox.co.il> writes:
>
> >> Quoting Junio C Hamano <gitster@pobox.com>:
> >> Perhaps they are most commonly used by the person who came up
> >> with that list first ;-)?
> >>
> >> I think "add" deserves to be there, I am not sure "apply" is.
> >
> > git add is supposed to be rare, no?
> > That's why git commit lists file additions/removals ...
>
> No.  You are talking in terms of pre-1.5 git.  The semantics of
> "git add" has been clarified since then --- it adds contents,
> and is not about telling git that there are new files it did not
> know so far.

In other words - git-add is also a (semantically good) alias for
git-update-index.

So you "add" files to the next commit. Whether they are "new" to git
or just changed it doesn't matter that much in that situation. And
git-commit will look at those files that have been "added".

Makes things a whole lot easier to explain. I didn't understand it
initially, now I'm completely sold on the concept.


m

  reply	other threads:[~2007-06-28  2:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25  6:40 most commonly used git commands? Michael S. Tsirkin
2007-06-25  7:10 ` Junio C Hamano
2007-06-25  7:17   ` Michael S. Tsirkin
2007-06-25  7:48     ` Junio C Hamano
2007-06-28  2:17       ` Martin Langhoff [this message]
2007-06-28  2:30         ` Josh Triplett
2007-06-25  7:51     ` Johannes Schindelin
2007-06-28  8:52       ` Alex Riesen
2007-06-28 13:08         ` Johannes Schindelin
2007-06-28 13:54           ` Johannes Sixt
2007-06-28 14:07             ` Johannes Schindelin
2007-06-28 14:29               ` Johannes Sixt
2007-06-28 14:49                 ` Johannes Sixt
2007-06-28 17:02                   ` [PATCH] git add: respect core.filemode even with unmerged entries in the index Johannes Schindelin
2007-06-29  6:57                     ` [PATCH] git add: respect core.filemode even with unmerged entriesin " Johannes Sixt
2007-06-29 10:07                       ` Johannes Schindelin
2007-06-29 10:20                         ` Junio C Hamano
2007-06-29 17:32                           ` [PATCH] git add: respect core.filemode with unmerged entries Johannes Schindelin
2007-06-29  8:36                     ` [PATCH] git add: respect core.filemode even with unmerged entries in the index Junio C Hamano
2007-06-29 10:06                       ` Johannes Schindelin
2007-06-30 13:14               ` most commonly used git commands? Alex Riesen
2007-06-30 14:31                 ` Johannes Schindelin
2007-06-30 22:35                   ` Alex Riesen
2007-07-01  9:16                     ` Jan Hudec
2007-07-01 16:49                       ` Alex Riesen
2007-06-28  1:37 ` Josh Triplett

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=46a038f90706271917j7abb4bddu21debafe3461c695@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mst@dev.mellanox.co.il \
    /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).