git: 563afbd6f0 - main - committer-guide: Add an anchor for the how to land a github pull request section.

Warner Losh <[email protected]>
Newsgroups gmane.os.freebsd.devel.cvs.doc
Message-ID <[email protected]>
The branch main has been updated by imp:

URL: https://cgit.FreeBSD.org/doc/commit/?id=563afbd6f0ea882e4696f0f6c5c7d0256d0c3b79

commit 563afbd6f0ea882e4696f0f6c5c7d0256d0c3b79
Author:     Warner Losh <[email protected]>
AuthorDate: 2021-06-16 21:36:02 +0000
Commit:     Warner Losh <[email protected]>
CommitDate: 2021-06-16 21:36:39 +0000

    committer-guide: Add an anchor for the how to land a github pull request section.
    
    So I can start dropping it into chats when people ask :)
    
    Sponsored by:           Netflix
---
 documentation/content/en/articles/committers-guide/_index.adoc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc
index e27ffcfe8e..9998694e0f 100644
--- a/documentation/content/en/articles/committers-guide/_index.adoc
+++ b/documentation/content/en/articles/committers-guide/_index.adoc
@@ -2303,6 +2303,7 @@ To github.com:gvnn3/freebsd-src.git
 At this point your work is now in your branch on +GitHub+ and you can
 share the link with other collaborators.
 
+[[github-pull-land]]
 === Landing a github pull request
 This section documents how to land a GitHub pull request that's submitted against the FreeBSD Git mirrors at GitHub.
 While this is not an official way to submit patches at this time, sometimes good fixes come in this way and it is easiest just to bring them into a committer's tree and have them pushed into the FreeBSD's tree from there.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/dev-commits-doc-all
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.