public inbox for [email protected]help / color / mirror / Atom feed
[PATCH 02/19] doc: Remove 'synchronized' from --no-sync 6+ messages / 4 participants [nested] [flat]
* [PATCH 02/19] doc: Remove 'synchronized' from --no-sync @ 2022-02-17 03:07 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 6+ messages in thread From: Justin Pryzby @ 2022-02-17 03:07 UTC (permalink / raw) Since it would be more accurate to say "unsynchronized". The corresponding change was made for pgupgrade.sgml in commit 410aa248 --- doc/src/sgml/ref/pg_rewind.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml index e808239aa5b..3231f67845a 100644 --- a/doc/src/sgml/ref/pg_rewind.sgml +++ b/doc/src/sgml/ref/pg_rewind.sgml @@ -210,7 +210,7 @@ PostgreSQL documentation to be written safely to disk. This option causes <command>pg_rewind</command> to return without waiting, which is faster, but means that a subsequent operating system crash can leave - the synchronized data directory corrupt. Generally, this option is + the data directory corrupt. Generally, this option is useful for testing but should not be used on a production installation. </para> -- 2.17.1 --8X7/QrJGcKSMr1RN Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0003-doc-json-log-dc686681e0799b12c40f44f85fc5bfd7fed4e57.patch" ^ permalink raw reply [nested|flat] 6+ messages in thread
* [PATCH 01/13] doc: Remove 'synchronized' from --no-sync @ 2022-02-17 03:07 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 6+ messages in thread From: Justin Pryzby @ 2022-02-17 03:07 UTC (permalink / raw) Since it would be more accurate to say "unsynchronized". The corresponding change was made for pgupgrade.sgml in commit 410aa248 --- doc/src/sgml/ref/pg_rewind.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml index e808239aa5b..3231f67845a 100644 --- a/doc/src/sgml/ref/pg_rewind.sgml +++ b/doc/src/sgml/ref/pg_rewind.sgml @@ -210,7 +210,7 @@ PostgreSQL documentation to be written safely to disk. This option causes <command>pg_rewind</command> to return without waiting, which is faster, but means that a subsequent operating system crash can leave - the synchronized data directory corrupt. Generally, this option is + the data directory corrupt. Generally, this option is useful for testing but should not be used on a production installation. </para> -- 2.17.1 --KlAEzMkarCnErv5Q Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0002-doc-pg_column_compression-we-say-method-not-algorith.patch" ^ permalink raw reply [nested|flat] 6+ messages in thread
* [PATCH 05/17] doc: Remove 'synchronized' from --no-sync @ 2022-02-17 03:07 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 6+ messages in thread From: Justin Pryzby @ 2022-02-17 03:07 UTC (permalink / raw) The corresponding change was made for pgupgrade.sgml in commit 410aa248 --- doc/src/sgml/ref/pg_rewind.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml index 33e6bb64ad6..c11f671855f 100644 --- a/doc/src/sgml/ref/pg_rewind.sgml +++ b/doc/src/sgml/ref/pg_rewind.sgml @@ -210,7 +210,7 @@ PostgreSQL documentation to be written safely to disk. This option causes <command>pg_rewind</command> to return without waiting, which is faster, but means that a subsequent operating system crash can leave - the synchronized data directory corrupt. Generally, this option is + the data directory corrupt. Generally, this option is useful for testing but should not be used on a production installation. </para> -- 2.17.1 --juZjCTNxrMaZdGZC Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0006-doc-json-log-dc686681e0799b12c40f44f85fc5bfd7fed4e57.patch" ^ permalink raw reply [nested|flat] 6+ messages in thread
* Time to add a Git .mailmap? @ 2024-10-31 10:37 Daniel Gustafsson <[email protected]> 0 siblings, 1 reply; 6+ messages in thread From: Daniel Gustafsson @ 2024-10-31 10:37 UTC (permalink / raw) To: PostgreSQL Hackers <[email protected]> When looking at our Git tree for a recent conference presentation I happened to notice that we have recently gained duplicate names in the shortlog. Not sure if we care enough to fix that with a .mailmap, but if we do the attached diff makes sure that all commits are accounted for a single committer entry. -- Daniel Gustafsson Attachments: [application/octet-stream] mailmap.diff (169B, ../../[email protected]/2-mailmap.diff) download | inline diff: diff --git a/.mailmap b/.mailmap new file mode 100644 index 0000000000..22d95d3484 --- /dev/null +++ b/.mailmap @@ -0,0 +1 @@ +Álvaro Herrera <[email protected]> ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Time to add a Git .mailmap? @ 2024-10-31 19:45 Nathan Bossart <[email protected]> parent: Daniel Gustafsson <[email protected]> 0 siblings, 1 reply; 6+ messages in thread From: Nathan Bossart @ 2024-10-31 19:45 UTC (permalink / raw) To: Daniel Gustafsson <[email protected]>; +Cc: PostgreSQL Hackers <[email protected]> On Thu, Oct 31, 2024 at 11:37:13AM +0100, Daniel Gustafsson wrote: > When looking at our Git tree for a recent conference presentation I happened to > notice that we have recently gained duplicate names in the shortlog. Not sure > if we care enough to fix that with a .mailmap, but if we do the attached diff > makes sure that all commits are accounted for a single committer entry. Seems reasonable to me. -- nathan ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Time to add a Git .mailmap? @ 2024-11-01 00:29 Michael Paquier <[email protected]> parent: Nathan Bossart <[email protected]> 0 siblings, 0 replies; 6+ messages in thread From: Michael Paquier @ 2024-11-01 00:29 UTC (permalink / raw) To: Nathan Bossart <[email protected]>; +Cc: Daniel Gustafsson <[email protected]>; PostgreSQL Hackers <[email protected]> On Thu, Oct 31, 2024 at 02:45:02PM -0500, Nathan Bossart wrote: > On Thu, Oct 31, 2024 at 11:37:13AM +0100, Daniel Gustafsson wrote: >> When looking at our Git tree for a recent conference presentation I happened to >> notice that we have recently gained duplicate names in the shortlog. Not sure >> if we care enough to fix that with a .mailmap, but if we do the attached diff >> makes sure that all commits are accounted for a single committer entry. > > Seems reasonable to me. +1. -- Michael Attachments: [application/pgp-signature] signature.asc (833B, ../../[email protected]/2-signature.asc) download ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2024-11-01 00:29 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2022-02-17 03:07 [PATCH 01/13] doc: Remove 'synchronized' from --no-sync Justin Pryzby <[email protected]> 2022-02-17 03:07 [PATCH 05/17] doc: Remove 'synchronized' from --no-sync Justin Pryzby <[email protected]> 2022-02-17 03:07 [PATCH 02/19] doc: Remove 'synchronized' from --no-sync Justin Pryzby <[email protected]> 2024-10-31 10:37 Time to add a Git .mailmap? Daniel Gustafsson <[email protected]> 2024-10-31 19:45 ` Re: Time to add a Git .mailmap? Nathan Bossart <[email protected]> 2024-11-01 00:29 ` Re: Time to add a Git .mailmap? Michael Paquier <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox