From: Timo Hirvonen <tihirvon@gmail.com>
To: Petr Baudis <pasky@suse.cz>
Cc: Johannes.Schindelin@gmx.de, git@vger.kernel.org
Subject: Re: Git BOF notes
Date: Sat, 22 Jul 2006 23:03:38 +0300 [thread overview]
Message-ID: <20060722230338.4ebcf7f8.tihirvon@gmail.com> (raw)
In-Reply-To: <20060722191652.GR13776@pasky.or.cz>
Petr Baudis <pasky@suse.cz> wrote:
> > Usually I start small projects as a single .c or .java file. Only after a
> > while, I think it is worth it to init a git database. So, I _always_ have
> > generated files lying around. And I would hate it if they were checked in
> > automatically. (Yeah, I could remove them, _then_ remove them from the
> > index, and then git-commit --amend. Ugly.)
>
> Can't you just do make clean before git init? Or you can prepare
> .gitignore before you check stuff in, so that the autogenerated files
> don't pollute your git status output. ;-)
I like git init-db as it is now. I don't want it to automatically add
files. GIT does what you ask it to do, not what it _thinks_ you want to
do.
--
http://onion.dynserv.net/~timo/
next prev parent reply other threads:[~2006-07-22 20:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 23:01 Git BOF notes Petr Baudis
2006-07-21 13:18 ` J. Bruce Fields
2006-07-21 14:42 ` Petr Baudis
2006-07-22 0:17 ` Johannes Schindelin
2006-07-22 3:22 ` Petr Baudis
2006-07-22 3:55 ` Johannes Schindelin
2006-07-22 19:16 ` Petr Baudis
2006-07-22 20:03 ` Timo Hirvonen [this message]
2006-07-23 22:53 ` Johannes Schindelin
2006-07-21 13:21 ` J. Bruce Fields
2006-07-21 14:31 ` Petr Baudis
2006-07-21 15:02 ` Alex Riesen
2006-07-22 20:12 ` Nguyễn Thái Ngọc Duy
2006-07-23 7:38 ` Alex Riesen
2006-07-24 9:06 ` Catalin Marinas
2006-07-24 11:47 ` Petr Baudis
2006-07-24 12:08 ` Nguyễn Thái Ngọc Duy
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=20060722230338.4ebcf7f8.tihirvon@gmail.com \
--to=tihirvon@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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.