<feed xmlns='http://www.w3.org/2005/Atom'>
<title>r-alacritty.git/.gitattributes, branch rahm</title>
<subtitle>My custom-patched version of alacritty.
</subtitle>
<link rel='alternate' type='text/html' href='https://git.josher.dev/cgit/r-alacritty.git/'/>
<entry>
<title>Remove custom merge strategy for changelog</title>
<updated>2021-08-27T22:11:20+00:00</updated>
<author>
<name>Christian Duerr</name>
<email>contact@christianduerr.com</email>
</author>
<published>2021-08-27T22:11:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.josher.dev/cgit/r-alacritty.git/commit/?id=cf35a2019162c6055e4a4c152976a424ba10869d'/>
<id>cf35a2019162c6055e4a4c152976a424ba10869d</id>
<content type='text'>
While the custom merge strategy can make things simpler in some
scenarios, it has repeatedly shown to silently introduce errors that
have to be manually spotted and corrected after the fact.

It's much more reliable and efficient to always manually oversee
potential conflicts, rather than letting them slip through half of the
time and having to contribute follow-up patches.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
While the custom merge strategy can make things simpler in some
scenarios, it has repeatedly shown to silently introduce errors that
have to be manually spotted and corrected after the fact.

It's much more reliable and efficient to always manually oversee
potential conflicts, rather than letting them slip through half of the
time and having to contribute follow-up patches.</pre>
</div>
</content>
</entry>
<entry>
<title>Add custom merge strategy for CHANGELOG.md</title>
<updated>2020-02-15T10:25:02+00:00</updated>
<author>
<name>Christian Duerr</name>
<email>contact@christianduerr.com</email>
</author>
<published>2020-02-15T10:25:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.josher.dev/cgit/r-alacritty.git/commit/?id=a842d6827c74108156f0f21e34ff93c2a7a349fb'/>
<id>a842d6827c74108156f0f21e34ff93c2a7a349fb</id>
<content type='text'>
The merge strategy `union` should hopefully reduce the number of
conflicts when trying to rebase the configuration file, since most of
the changes are simple additions anyways.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The merge strategy `union` should hopefully reduce the number of
conflicts when trying to rebase the configuration file, since most of
the changes are simple additions anyways.</pre>
</div>
</content>
</entry>
</feed>
