See issue 349 for discussion of these changes.

# Release checklist
- [NA] Authors updated in `cf-conventions.adoc`?
- [NA] Next version in `cf-conventions.adoc` up to date? Versioning inspired by 
[SemVer](https://urldefense.us/v3/__https://semver.org__;!!G2kpM7uM-TzIFchu!hQgyxRXTKvpetADIxmFvwz7YuKdN_k6pMbdKcq_FNy7CfrLb-H8U203i00BaxtaJedwppnjGeDY$
 ).
- [Y] `history.adoc` up to date?
- [NA] Conformance document up-to-date?

# For maintainers
After the merge remember to delete the source branch.
Tags are set at the conclusion of the annual meeting; until then `master` 
always is a draft for the next version.

You can view, comment on, or merge this pull request online at:

  
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/350__;!!G2kpM7uM-TzIFchu!hQgyxRXTKvpetADIxmFvwz7YuKdN_k6pMbdKcq_FNy7CfrLb-H8U203i00BaxtaJedwpdPxuCOs$
 

-- Commit Summary --

  * issue 349, delete Conventions attribute from ex 7.15 and 7.16
  * updated history.adoc

-- File Changes --

    M ch07.adoc (2)
    M history.adoc (3)

-- Patch Links --

https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/350.patch__;!!G2kpM7uM-TzIFchu!hQgyxRXTKvpetADIxmFvwz7YuKdN_k6pMbdKcq_FNy7CfrLb-H8U203i00BaxtaJedwp15rj2c0$
 
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/350.diff__;!!G2kpM7uM-TzIFchu!hQgyxRXTKvpetADIxmFvwz7YuKdN_k6pMbdKcq_FNy7CfrLb-H8U203i00BaxtaJedwp97CguFQ$
 

-- 
Reply to this email directly or view it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/350__;!!G2kpM7uM-TzIFchu!hQgyxRXTKvpetADIxmFvwz7YuKdN_k6pMbdKcq_FNy7CfrLb-H8U203i00BaxtaJedwpdPxuCOs$
 
You are receiving this because you are subscribed to this thread.

Message ID: <cf-convention/cf-conventions/pull/[email protected]>

This list forwards relevant notifications from Github.  It is distinct from 
[email protected], although if you do nothing, a subscription to the 
UCAR list will result in a subscription to this list.
To unsubscribe from this list only, send a message to 
[email protected].

Reply via email to