zsh-workers
 help / color / mirror / code / Atom feed
From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: zsh-workers@zsh.org
Cc: Peter Stephenson <p.stephenson@samsung.com>
Subject: Re: Access to CVS
Date: Sun, 16 Dec 2012 04:50:13 -0500	[thread overview]
Message-ID: <20121216095012.GA68923@redoubt.spodhuis.org> (raw)
In-Reply-To: <20121214192945.GA40810@redoubt.spodhuis.org>

On 2012-12-14 at 14:29 -0500, Phil Pennock wrote:
> "git commit -a" automatically finds files which are tracked and have
> been modified, but doesn't pick up files newly tracked.  "git add"
> starts tracking a file.

*sigh* Dumbass mis-statement on my part, sorry.

"git commit -a" doesn't pick up newly created files, because they're not
tracked (except just enough to say "not tracked" and to be handled by
commands like "git stash").

> If you want to be more selective, then for each file changed, "git add"
> it to stage it in the index for the next commit, then just "git commit"
> which will only commit the manually-staged files.

To be clear: "git add" is not "add tracking this new file to the
repository", it's "add this file to the index of changes to be in the
next commit", where such a change _might_ be the creation of a new file,
or might simply be "I changed it, include it".

-Phil


  parent reply	other threads:[~2012-12-16  9:50 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-14 14:44 Oliver Kiddle
2012-12-14 15:09 ` Peter Stephenson
2012-12-14 19:29   ` Phil Pennock
2012-12-15 18:09     ` Peter Stephenson
2012-12-15 19:07       ` Wayne Davison
2012-12-15 21:07         ` Aaron Schrab
2012-12-16  9:50     ` Phil Pennock [this message]
2012-12-16 18:14       ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
2012-12-04 22:32 Vin Shelton
2012-12-04 22:51 ` Phil Pennock
2012-12-05  0:33   ` Oliver Kiddle
2012-12-05  3:14     ` Phil Pennock
2012-12-05  9:40       ` Bart Schaefer
2012-12-05 11:26         ` Phil Pennock
2012-12-05 12:11           ` Frank Terbeck
2012-12-05 21:13             ` Aaron Schrab
2012-12-05 23:34               ` Aaron Schrab
2012-12-05 19:50           ` Peter Stephenson
2012-12-06 19:59             ` Peter Stephenson
2012-12-07  0:05             ` Aaron Schrab
2012-12-07  7:13               ` Alex Ogier
2012-12-07  9:34                 ` Frank Terbeck
2012-12-07 15:11                 ` Aaron Schrab
2012-12-07 15:37                   ` François Revol
2012-12-07 16:06                     ` Aaron Schrab
2012-12-07  9:29               ` Frank Terbeck
2012-12-07 10:57                 ` Christian Neukirchen
2012-12-07 11:08                   ` Frank Terbeck
2012-12-07 11:38                     ` Frank Terbeck
2012-12-07 15:31                 ` Bart Schaefer
2012-12-07 16:01                   ` Aaron Schrab
2012-12-07  9:49               ` Peter Stephenson
2012-12-07 11:03                 ` Frank Terbeck
2013-03-17 14:55                   ` Simon Ruderich
2013-04-04 13:38                     ` Simon Ruderich
2012-12-11 23:05                 ` Oliver Kiddle
2012-12-12  8:23                   ` Frank Terbeck
2012-12-12 15:31                     ` Aaron Schrab
2012-12-12 17:25                     ` Oliver Kiddle
2012-12-12 18:57                       ` Bart Schaefer
2012-12-13 12:58                         ` Oliver Kiddle
2012-12-13 14:57                           ` Simon Ruderich
2012-12-13 15:37                           ` Bart Schaefer
2012-12-13 16:03                             ` Aaron Schrab
2012-12-13 15:50                           ` Aaron Schrab
2012-12-13 16:13                           ` Peter Stephenson
2012-12-13 16:20                             ` Bart Schaefer
2012-12-13 19:13                               ` Phil Pennock
2012-12-14  9:22                                 ` Frank Terbeck
2012-12-15 18:57                           ` Wayne Davison
2012-12-05  2:26   ` Vin Shelton

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=20121216095012.GA68923@redoubt.spodhuis.org \
    --to=zsh-workers+phil.pennock@spodhuis.org \
    --cc=p.stephenson@samsung.com \
    --cc=zsh-workers@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).