summaryrefslogtreecommitdiff
path: root/bin/equery
diff options
context:
space:
mode:
authorMatt Turner <mattst88@gentoo.org>2020-12-20 17:12:49 -0500
committerMatt Turner <mattst88@gentoo.org>2020-12-31 14:44:17 -0500
commit9f01c8b098484866974407bb74680debf0d64e4f (patch)
tree1afcbba825d6dfd8407ee80d38278739e08ffdfc /bin/equery
parent2f572237ebbf2be2b56803394a40d5c4938cbdb7 (diff)
downloadgentoolkit-9f01c8b098484866974407bb74680debf0d64e4f.tar.gz
bin: Add merge-driver-ekeyword
Since the KEYWORDS=... assignment is a single line, git struggles to handle conflicts. When rebasing a series of commits that modify the KEYWORDS=... it's usually easier to throw them away and reapply on the new tree than it is to manually handle conflicts during the rebase. git allows a 'merge driver' program to handle conflicts; this program handles conflicts in the KEYWORDS=... assignment. E.g., given an ebuild with these keywords: KEYWORDS="~alpha amd64 arm arm64 ~hppa ppc ppc64 x86" One developer drops the ~alpha keyword and pushes to gentoo.git, and another developer stabilizes hppa. Without this merge driver, git requires the second developer to manually resolve the conflict which is tedious and prone to mistakes when rebasing a long series of patches. With the custom merge driver, it automatically resolves the conflict. To use the merge driver, configure your gentoo.git as such: gentoo.git/.git/config: [merge "keywords"] name = KEYWORDS merge driver driver = merge-driver-ekeyword %O %A %B %P gentoo.git/.git/info/attributes: *.ebuild merge=keywords Signed-off-by: Matt Turner <mattst88@gentoo.org>
Diffstat (limited to 'bin/equery')
0 files changed, 0 insertions, 0 deletions