Jon,

I was told to put changes to docs that apply to the current version in 
the current branch and then when that branch is merged with master it 
shows up there. So when working on docs for 2.4.x you have to do a git 
checkout of that branch first then make your changes. And changes that 
apply to only master go in there.

As I recall you committed your change to master so it resides there. I 
think there is a cherry pick thing you can do but don't know enough 
about that to advise you on that.

John

Jon Elson wrote:
> About a month ago, I made some substantial updates to the ppmc driver
> section of the Integrator's Manual
> (file: docs/src/drivers/pico_ppmc.lyx) but these changes have not showed
> up yet in the main version of the manual
> linked from the Wiki page.  Is there something I need to do to push
> these changes into the right branch of the
> source tree so it gets built into the public version of the manual?
>
> Thanks,
>
> Jon
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Emc-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>    

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to