diff options
| author | J William Piggott | 2017-05-30 02:47:34 +0200 |
|---|---|---|
| committer | J William Piggott | 2017-05-31 17:36:47 +0200 |
| commit | 80008bcae9a1aed3d38507a319155a69c4414509 (patch) | |
| tree | 101b7ea7e5c9ac241dddae7289dba1b9f87214d1 /Documentation/howto-contribute.txt | |
| parent | docs: update howto-contribute.txt (diff) | |
| download | kernel-qcow2-util-linux-80008bcae9a1aed3d38507a319155a69c4414509.tar.gz kernel-qcow2-util-linux-80008bcae9a1aed3d38507a319155a69c4414509.tar.xz kernel-qcow2-util-linux-80008bcae9a1aed3d38507a319155a69c4414509.zip | |
docs: move source-code-management.txt to README
source-code-management.txt and README had similar content so combine
them in README.
Change Documentation/source-code-management.txt references to README.
Remove Documentation/source-code-management.txt.
Move IRC Channel information to README
Expand information about git branches and tags in README.
Add workflow to README; written by Karel Zak <kzak@redhat.com>
Signed-off-by: J William Piggott <elseifthen@gmx.com>
Diffstat (limited to 'Documentation/howto-contribute.txt')
| -rw-r--r-- | Documentation/howto-contribute.txt | 18 |
1 files changed, 4 insertions, 14 deletions
diff --git a/Documentation/howto-contribute.txt b/Documentation/howto-contribute.txt index fc2c50330..71b9ed771 100644 --- a/Documentation/howto-contribute.txt +++ b/Documentation/howto-contribute.txt @@ -5,17 +5,16 @@ CONTENTS Coding Style Various Notes Standards Compliance - IRC Channel Sending Patches - * send your patches to the mailing list or to the project maintainer. + * send your patches to the mailing list. See ../README. * email is accepted as an inline patch with, or without, a git pull request. Pull request emails need to include the patch set for review - purposes. See howto-pull-request.txt and source-code-management.txt - for git repository instructions. + purposes. See howto-pull-request.txt and ../README for git repository + instructions. * email attachments are difficult to review and not recommended. Hint: use git send-email. @@ -64,7 +63,7 @@ Patching Process Hint: use the --subject-prefix='PATCH v2' option with 'git format-patch' * using a git repository for (re)submissions can make life easier. - See howto-pull-request.txt and source-code-management.txt. + See howto-pull-request.txt and ../README. * all patch submissions are either commented, rejected, or accepted. If the maintainer rejects a patch set it is pointless to resubmit it. @@ -190,12 +189,3 @@ Standards Compliance http://pubs.opengroup.org/onlinepubs/7908799/xcuix.html -IRC Channel - - * #util-linux at freenode.net: - - irc://chat.freenode.net/util-linux - - This channel is for developers and project maintainers. For end users - it is recommended to utilize the distribution's IRC channel or support - forum. |