<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://etherboot.org/dokuwiki-2017-02-19b/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://etherboot.org/dokuwiki-2017-02-19b/feed.php">
        <title>Etherboot/gPXE Wiki wiki:user:mdc:notes:git</title>
        <description></description>
        <link>http://etherboot.org/dokuwiki-2017-02-19b/</link>
        <image rdf:resource="http://etherboot.org/dokuwiki-2017-02-19b/lib/tpl/monobook/images/favicon.ico" />
       <dc:date>2026-04-17T04:41:37-07:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://etherboot.org/dokuwiki-2017-02-19b/wiki/user/mdc/notes/git/merging-commits?rev=1244552303&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://etherboot.org/dokuwiki-2017-02-19b/lib/tpl/monobook/images/favicon.ico">
        <title>Etherboot/gPXE Wiki</title>
        <link>http://etherboot.org/dokuwiki-2017-02-19b/</link>
        <url>http://etherboot.org/dokuwiki-2017-02-19b/lib/tpl/monobook/images/favicon.ico</url>
    </image>
    <item rdf:about="http://etherboot.org/dokuwiki-2017-02-19b/wiki/user/mdc/notes/git/merging-commits?rev=1244552303&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-09T05:58:23-07:00</dc:date>
        <title>wiki:user:mdc:notes:git:merging-commits</title>
        <link>http://etherboot.org/dokuwiki-2017-02-19b/wiki/user/mdc/notes/git/merging-commits?rev=1244552303&amp;do=diff</link>
        <description>Merging multiple git commits into a single commit

Here is a link to a good article on this:
https://cswiki.cs.byu.edu/cs431/index.php/Git_Basics#Flattening_Revision_History
The useful part:

Flattening Revision History

When working on a feature in an existing code base, you'll probably want to commit often to keep track of your progress. However, when you finish your feature and you're ready to send a patch to an upstream repository, you probably won't want to send them all of your revision hi…</description>
    </item>
</rdf:RDF>
