Thanks.
I read "Generate Patch" section and saw no Git mention. Did not read
"Working.." section as I did not expect to need it any time soon.
It is good to know.
Regards,
Alex.
Personal blog: http://blog.outerthoughts.com/
LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch
- Time is
If you read the HowToContribute page you will see it described there. I's
supported, you just need to apply the patch with -p1 instead of -p0
http://wiki.apache.org/solr/HowToContribute#Working_With_Patches
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
Solr Training
I thought git patch format was different from svn's. Would that cause
issues?
Regard,
Alex
On 21 Mar 2013 05:53, "Jan Høydahl" wrote:
> See http://wiki.apache.org/solr/HowToContribute
>
> Whether you choose to work locally with a GIT checkout or SVN is up to
> you. At the end of the day, w
Committers mostly use ant+ivy, so that will most likely be more stable. Both
Eclipse and IDEA are frequently in use by committers so both are safe choices.
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
Solr Training - www.solrtraining.com
21. mars 2013 kl. 11:10 skre
How about deciding on Maven or Ant + Ivy. On the other hand I need another
suggestion whether using Eclipse or Intellij IDEA. What developers use in
common?
2013/3/21 Jan Høydahl
> See http://wiki.apache.org/solr/HowToContribute
>
> Whether you choose to work locally with a GIT checkout or SVN i
See http://wiki.apache.org/solr/HowToContribute
Whether you choose to work locally with a GIT checkout or SVN is up to you. At
the end of the day, when you want to contribute stuff back, you'd generate a
patch and attach it to JIRA. SVN is the main repo, so if you want to be 100% in
sync, choos
