From: "Tor Arvid Lund" <torarvid@gmail.com>
To: "Ivan Senji" <ivan.senji@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: getting started with git
Date: Fri, 14 Nov 2008 13:56:14 +0100 [thread overview]
Message-ID: <1a6be5fa0811140456j10fd8703w74e485571e3c70af@mail.gmail.com> (raw)
In-Reply-To: <20497802.post@talk.nabble.com>
On Fri, Nov 14, 2008 at 11:16 AM, Ivan Senji <ivan.senji@gmail.com> wrote:
> On each location that i develop some project and configuration files are
> different. But i would like them to be in the repository as a starting point
> when checking out a project (example: opening a project on a dfferent OS in
> eclipse... eclipse will find an error in the path to jdk and ask me to fix
> that error by selecting a different jdk).
>
> How to achieve that these files are in the repository but that any further
> changes to them are not commited (or are commited localy but not pushed to a
> remote repository)?
Hi,
Well, if it were me, I think I would commit that eclipse config file
under a different name... Say, ".classpath.defaults" instead of
".classpath". Then your README file could tell your users to start by
copying the .classpath.defaults to .classpath, and update its contents
as necessary. Put .classpath in your .gitignore file, so it won't be
committed to the repository.
-Tor Arvid-
next prev parent reply other threads:[~2008-11-14 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 10:16 getting started with git Ivan Senji
2008-11-14 12:56 ` Tor Arvid Lund [this message]
2008-11-14 14:29 ` Lars Hoss
-- strict thread matches above, loose matches on Subject: below --
2011-03-20 21:08 Industrywide breakthrough innovation - Git as a key role of distribution Kalle Launiala
2011-03-21 13:59 ` Getting started with git Jonathan Nieder
2011-03-22 0:21 ` Kalle Launiala
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=1a6be5fa0811140456j10fd8703w74e485571e3c70af@mail.gmail.com \
--to=torarvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=ivan.senji@gmail.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).