| Not that it answers your question directly, but you can use “git update-index —assume-unchanged” to make it appear that you haven’t changed the file and so not to be considered as a diff when pulling.
I have a wrapper script called “git forget” because it’s easier to type.
https://github.com/alblue/scripts/blob/main/git-forgetSent from my iPhone 📱 On 18 Aug 2021, at 18:28, Christoph Läubrich <laeubi@xxxxxxxxxxxxxx> wrote:
One thing I always wonder, most projects in platform use a project specific setting
org.eclipse.jdt.core.compiler.problem.invalidJavadoc=error
but with this settings enabled there are hundreds of errors and the workspace is nearly unusable.
So my first task is always to change the error to warning to at least get a valid build.
I can understand that one want to have valid javadoc, but enabling this and not fixing the errors seems strange to me. So how is this to be handeled? I really don't like to change/reset settings each time I pull the changes from the repo...
_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
|
