Clarify that the vendor merge commits should have proper commit messages
ClosedPublic
Actions

Authored by markj on Apr 13 2021, 1:41 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Thu, May 9, 12:42 AM

	Unknown Object (File)
	Wed, May 8, 9:56 PM

	Unknown Object (File)
	May 1 2024, 5:21 PM

	Unknown Object (File)
	Apr 26 2024, 3:14 PM

	Unknown Object (File)
	Apr 10 2024, 8:54 PM

	Unknown Object (File)
	Apr 7 2024, 5:45 PM

	Unknown Object (File)
	Mar 11 2024, 5:19 AM

	Unknown Object (File)
	Jan 14 2024, 10:42 PM

View All 17 Files

Subscribers

None

Details

Reviewers

imp

Commits

R9:6f71dc766bc6: Clarify that the vendor merge commits should have proper commit messages

Diff Detail

Repository

R9 FreeBSD doc repository

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

markj requested review of this revision.Apr 13 2021, 1:41 PM

markj created this revision.

Harbormaster completed remote builds in B38558: Diff 87376.Apr 13 2021, 1:42 PM

markj added a reviewer: imp.Apr 13 2021, 1:50 PM

great! You beat me to the punch :)
thanks

This revision is now accepted and ready to land.Apr 13 2021, 7:49 PM

Closed by commit R9:6f71dc766bc6: Clarify that the vendor merge commits should have proper commit messages (authored by markj). · Explain WhyApr 19 2021, 7:54 PM

This revision was automatically updated to reflect the committed changes.

markj added a commit: R9:6f71dc766bc6: Clarify that the vendor merge commits should have proper commit messages.

Revision Contents
Changeset List

Path

Size

documentation/

content/

en/

articles/

committers-guide/

_index.adoc

1 line

Diff 87743

View Options

documentation/content/en/articles/committers-guide/_index.adoc

Clarify that the vendor merge commits should have proper commit messagesClosedPublicActions