GitHub user robertkowalski opened a pull request:

    https://github.com/apache/couchdb-fauxton/pull/99

    Move parts of fauxton.less to formstyles.less

    Fauxton.less is pretty hot code when you look at the commit
    frequency. This commit just moves the parts of todays
    fauxton.less to the new formstyles.less file to avoid a
    long living branch with endless merge commits. This way
    my colleagues can already use the new templates.less file
    and have the advantage of a small separate template.less file
    as soon as possible.
    
    Based on the work of Jenn Schiffer <[email protected]>
    (@jennschiffer) and Sue Lockwood <[email protected]>
    (@deathbearbrown)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/robertkowalski/couchdb-fauxton formstyles.less

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-fauxton/pull/99.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #99
    
----
commit 7cadbba905329e7f0d367b3dfa69502bf199b055
Author: Robert Kowalski <[email protected]>
Date:   2014-10-15T15:07:42Z

    Move parts of fauxton.less to formstyles.less
    
    Fauxton.less is pretty hot code when you look at the commit
    frequency. This commit just moves the parts of todays
    fauxton.less to the new formstyles.less file to avoid a
    long living branch with endless merge commits. This way
    my colleagues can already use the new templates.less file
    and have the advantage of a small separate template.less file
    as soon as possible.
    
    Based on the work of Jenn Schiffer <[email protected]>
    (@jennschiffer) and Sue Lockwood <[email protected]>
    (@deathbearbrown)

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to