ollow" link="external"> [hidden email]
>> >> For additional commands, e-mail: > >> href="x-msg://149/user/SendEmail.jtp?type=node&node=4022419&i=5"
>> >> target="_top"
low" link="external"> [hidden email]
>> >> For additional commands, e-mail: > >> href="x-msg://149/user/SendEmail.jtp?type=node&node=4022419&i=5"
>> >> target="_top" rel="
AFAIK if you set svn:ignore * then it won't ignore files and directories that
are in source control.
~ David
On Nov 26, 2012, at 1:41 PM, sarowe [via Lucene] wrote:
I've always put patches up one level from checked out dirs: svn diff >
../PROJECT-.patch; patch -p0 < ../PROJECT-.patch.
I've always put patches up one level from checked out dirs: svn diff >
../PROJECT-.patch; patch -p0 < ../PROJECT-.patch.
For stuff that should be ignored by everybody (or that wouldn't cause trouble
for others), we could add them to the svn:ignore list for the directory they're
in?
Alt
Hi David,
there are actually 2 reasons for this check:
- It prevents that you forget to add files before committing. We had this quite
often, causing unbuildable sources and Jenkins failures.
- Prevent test cases from leaving files around at wrong places. This was the
original idea behind the ta
How about doing the dirty checks on sub-directories only? This way I can keep
the random .patch files & miscellany around in the root.
The IDE files are a special circumstance for my setup because I use symbolic
links to the IDE files in dev-tools so that I can easily see how my IDE setup
is d
This is still a problem for people working with git-svn, but I admit
it makes sense to have a precommit target that assumes a "supported"
configuration, whatever it may be, and enforces strict checks rather
than support multiple configurations with next to nothing.
Dawid
On Mon, Nov 26, 2012 at 5
I think the idea is to catch files you forgot to svn add.
For IDE files, you should just svn ignore them?
Mike McCandless
http://blog.mikemccandless.com
On Mon, Nov 26, 2012 at 9:46 AM, David Smiley (@MITRE.org)
wrote:
> "ant precommit" will check if the source tree is "dirty" (i.e. contains f
