git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Herland <johan@herland.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>,
	"Randal L. Schwartz" <merlyn@stonehenge.com>,
	Jakub Narebski <jnareb@gmail.com>
Subject: Re: [PATCH] user-manual: Add section on ignoring files
Date: Wed, 16 May 2007 09:28:00 +0200	[thread overview]
Message-ID: <200705160928.00900.johan@herland.net> (raw)
In-Reply-To: <7vhcqdha4b.fsf@assigned-by-dhcp.cox.net>

On Wednesday 16 May 2007, Junio C Hamano wrote:
> Johan Herland <johan@herland.net> writes:
> 
> > +This typically includes files generated by a build process or temporary
> > +backup files made by your editor. Of course, 'not' tracking files with git
> > +is just a matter of 'not' calling "`git add`" on them. But it quickly becomes
> > +annoying to have these untracked files lying around; e.g. they make
> > +"`git add .`" and "`git commit -a`" practically useless, and they keep
> 
> I think we would want to s/and "`git commit -a`//; if you start
> tracking the file, .gitignore would not interfere with it AFAIK.

You're right. "git commit -a" doesn't actually add untracked files at all 
(you still have to do "git add", anyway). Don't know what I was thinking.
Feel free to edit.


...Johan

-- 
Johan Herland, <johan@herland.net>
www.herland.net

  reply	other threads:[~2007-05-16  7:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 22:47 [PATCH] user-manual: Add section on ignoring files Johan Herland
2007-05-15 23:24 ` Jakub Narebski
2007-05-15 23:31   ` Johan Herland
2007-05-15 23:30 ` Junio C Hamano
2007-05-16  0:31   ` Johan Herland
2007-05-16  0:42     ` Junio C Hamano
2007-05-16  7:28       ` Johan Herland [this message]
2007-05-16  3:30     ` J. Bruce Fields
2007-05-16  7:38       ` Johan Herland

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=200705160928.00900.johan@herland.net \
    --to=johan@herland.net \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=junkio@cox.net \
    --cc=merlyn@stonehenge.com \
    /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).