grub2/0075-Mark-po-exclude.pot-as-binary-so-git-won-t-try-to-di.patch

From 126f6952b853ea67e784650ed12f365ab7988f51 Mon Sep 17 00:00:00 2001
From: Peter Jones <pjones@redhat.com>
Date: Wed, 22 Jul 2015 11:21:01 -0400
Subject: [PATCH 075/206] Mark po/exclude.pot as binary so git won't try to
 diff nonprintables.

Signed-off-by: Peter Jones <pjones@redhat.com>
---
 .gitattributes | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 .gitattributes

diff --git a/.gitattributes b/.gitattributes
new file mode 100644
index 00000000000..33ffaa40460
--- /dev/null
+++ b/.gitattributes
@@ -0,0 +1 @@
+po/exclude.pot binary
-- 
2.15.0
Dump a bunch of work-in-progress patches for now. Signed-off-by: Peter Jones <pjones@redhat.com> 2018-01-17 22:04:09 +00:00			`From 126f6952b853ea67e784650ed12f365ab7988f51 Mon Sep 17 00:00:00 2001`
Reconcile even harder, so that it actually works. Signed-off-by: Peter Jones <pjones@redhat.com> 2015-07-22 14:14:34 +00:00			`From: Peter Jones <pjones@redhat.com>`
			`Date: Wed, 22 Jul 2015 11:21:01 -0400`
Update grub2 for f28 - Try to fix things for new compiler madness. I really don't know why gcc decided __attribute__((packed)) on a "typedef struct" should imply __attribute__((align (1))) and that it should have a warning that it does so. The obvious behavior would be to keep the alignment of the first element unless it's used in another object or type that /also/ hask the packed attribute. Why should it change the default alignment at all? - Merge in the BLS patches Javier and I wrote. - Attempt to fix pmtimer initialization failures to not be super duper slow. Signed-off-by: Peter Jones <pjones@redhat.com> 2018-02-27 18:56:41 +00:00			`Subject: [PATCH 075/206] Mark po/exclude.pot as binary so git won't try to`
Dump a bunch of work-in-progress patches for now. Signed-off-by: Peter Jones <pjones@redhat.com> 2018-01-17 22:04:09 +00:00			`diff nonprintables.`
Reconcile even harder, so that it actually works. Signed-off-by: Peter Jones <pjones@redhat.com> 2015-07-22 14:14:34 +00:00
			`Signed-off-by: Peter Jones <pjones@redhat.com>`
			`---`
			`.gitattributes \| 1 +`
			`1 file changed, 1 insertion(+)`
			`create mode 100644 .gitattributes`

			`diff --git a/.gitattributes b/.gitattributes`
			`new file mode 100644`
Update grub2 for f28 - Try to fix things for new compiler madness. I really don't know why gcc decided __attribute__((packed)) on a "typedef struct" should imply __attribute__((align (1))) and that it should have a warning that it does so. The obvious behavior would be to keep the alignment of the first element unless it's used in another object or type that /also/ hask the packed attribute. Why should it change the default alignment at all? - Merge in the BLS patches Javier and I wrote. - Attempt to fix pmtimer initialization failures to not be super duper slow. Signed-off-by: Peter Jones <pjones@redhat.com> 2018-02-27 18:56:41 +00:00			`index 00000000000..33ffaa40460`
Reconcile even harder, so that it actually works. Signed-off-by: Peter Jones <pjones@redhat.com> 2015-07-22 14:14:34 +00:00			`--- /dev/null`
			`+++ b/.gitattributes`
			`@@ -0,0 +1 @@`
			`+po/exclude.pot binary`
			`--`
Update grub2 for f28 - Try to fix things for new compiler madness. I really don't know why gcc decided __attribute__((packed)) on a "typedef struct" should imply __attribute__((align (1))) and that it should have a warning that it does so. The obvious behavior would be to keep the alignment of the first element unless it's used in another object or type that /also/ hask the packed attribute. Why should it change the default alignment at all? - Merge in the BLS patches Javier and I wrote. - Attempt to fix pmtimer initialization failures to not be super duper slow. Signed-off-by: Peter Jones <pjones@redhat.com> 2018-02-27 18:56:41 +00:00			`2.15.0`
Reconcile even harder, so that it actually works. Signed-off-by: Peter Jones <pjones@redhat.com> 2015-07-22 14:14:34 +00:00