Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of willem.jiang@gmail.com
 designates 209.85.212.45 as permitted sender)
Message-ID: <4ED63C78.8090402@gmail.com>
Date: Wed, 30 Nov 2011 22:23:52 +0800
From: Willem Jiang <willem.jiang@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: dev@camel.apache.org
Subject: Re: The svn:ignore property isn't settled down on trunk
References: <1322646813856-5035110.post@n5.nabble.com>
In-Reply-To: <1322646813856-5035110.post@n5.nabble.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi,
Just commit a quick fix for it.
BTW, I'm using git[1] to work on apache camel code now, 
it could be more simple to avoid this issue by add a .gitignore file in 
the project root.

[1]http://git.apache.org/

On Wed Nov 30 17:53:33 2011, bvahdat wrote:
> Hi Devs,
>
> That would be great if some committer would update the svn:ignore property
> on the trunk (as an example camel-jclouds/target folder is considered as an
> outgoing-change on my IDE, or .classpath&  .project by some other camel
> components).
>
> IMHO this would make life easier for the commiters (while commiting local
> workspace changes directly into svn) as well as for the people intending to
> provide a patch, so that they should not select what to include inside the
> patch what not (out of a lot outgoing changes).
>
> Babak
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/The-svn-ignore-property-isn-t-settled-down-on-trunk-tp5035110p5035110.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>


-- 
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog:    http://willemjiang.blogspot.com (English)
         http://jnn.javaeye.com (Chinese)
Twitter: willemjiang 
Weibo: willemjiang