git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: llucianf <llucianf@gmail.com>
To: git@vger.kernel.org
Subject: Re: gitignore design
Date: Fri, 29 Jul 2011 05:16:14 -0700 (PDT)	[thread overview]
Message-ID: <1311941774976-6633332.post@n2.nabble.com> (raw)
In-Reply-To: <4E32A2D2.9060007@hupie.com>

is not a contradiction. i need project files into repo so whenever i clone
the project on diff machine i need them there.
but during development i dont need them to be 'taken into account' by git. 
the purpose of this topic is for me to understand why git dont use the
simple cvs approach on this matter.
why i cant just enumerate some files into .gitignore file and have git
simply ignore them without removing them from repo?

--
View this message in context: http://git.661346.n2.nabble.com/gitignore-design-tp6632987p6633332.html
Sent from the git mailing list archive at Nabble.com.

  reply	other threads:[~2011-07-29 12:16 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 [this message]
2011-07-29 12:27         ` Jakub Narebski
2011-07-29 12:44           ` llucianf
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=1311941774976-6633332.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).