From: llucianf <llucianf@gmail.com>
To: git@vger.kernel.org
Subject: Re: gitignore design
Date: Fri, 29 Jul 2011 05:44:41 -0700 (PDT) [thread overview]
Message-ID: <1311943481799-6633412.post@n2.nabble.com> (raw)
In-Reply-To: <m3y5zhqnlv.fsf@localhost.localdomain>
im sure cvs doesnt require you to remove files from repo in order to ignore
them. i used cvs for years and its ingonre policy is simple and effective.
you just put the files/patterns into ignore file and things happen aka they
are ignored.
with this very intelligent git this simple thing is not so simple. of course
there are workarounds (like the template example you gave) but they are
clumsy.
im just trying to understand why git ignore mechanism cant just read the
.gitignore file and obey to those ignore rules without asking you to do
fancy voodoo operations such removing those files from repo.
--
View this message in context: http://git.661346.n2.nabble.com/gitignore-design-tp6632987p6633412.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2011-07-29 12:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 10:20 gitignore design llucianf
2011-07-29 11:51 ` Ferry Huberts
2011-07-29 12:01 ` llucianf
2011-07-29 12:08 ` Ferry Huberts
2011-07-29 12:16 ` llucianf
2011-07-29 12:27 ` Jakub Narebski
2011-07-29 12:44 ` llucianf [this message]
2011-07-29 12:57 ` Jakub Narebski
2011-07-29 14:01 ` Ferry Huberts
2011-07-29 12:19 ` Jakub Narebski
2011-07-29 12:58 ` Johannes Sixt
2011-07-29 13:19 ` Jakub Narebski
2011-07-29 13:31 ` Johannes Sixt
2011-07-29 21:39 ` Jakub Narebski
2011-07-30 3:10 ` Nguyen Thai Ngoc Duy
2011-07-30 6:45 ` Piotr Krukowiecki
2011-07-30 13:22 ` Nguyen Thai Ngoc Duy
2011-07-30 15:52 ` Piotr Krukowiecki
2011-07-30 16:01 ` Clemens Buchacher
2011-07-29 16:44 ` Philip Oakley
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=1311943481799-6633412.post@n2.nabble.com \
--to=llucianf@gmail.com \
--cc=git@vger.kernel.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.
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).