From: Karel Zak <kzak@redhat.com>
To: J William Piggott <elseifthen@gmx.com>
Cc: "Rüdiger Meier" <sweet_f_a@gmx.de>,
util-linux <util-linux@vger.kernel.org>
Subject: Re: versioning
Date: Mon, 29 May 2017 12:22:45 +0200 [thread overview]
Message-ID: <20170529102245.cbwndbup2nwbbcna@ws.net.home> (raw)
In-Reply-To: <671ded97-cdf5-6f01-393d-a96372382f13@gmx.com>
On Sat, May 27, 2017 at 02:55:41PM -0400, J William Piggott wrote:
>
>
> On 05/23/2017 04:54 PM, J William Piggott wrote:
> >
> > I think I will submit a patch to add something to Documentation about
> > this so that someone else might not ask the same dumb questions.
>
> I started on this and noticed that the source-code-management.txt and
> README files are very similar. README actually has a more complete
> version schema breakdown. Is there any reason that they should not be
> combined into a single file?
No problem, but I'd like to keep all most important information
(=links, addresses, etc.) in the README file.
Send patch :-)
> README includes the mailing list. Is there any reason that the IRC
> channel shouldn't be there instead of in howto-contribute.txt?
Send patch :-)
> The howto-contribute.txt file says patches can be sent to the mailing
> list or directly to Karel, and points to README for the addresses. Is
> there any reason not to have Karel's email contact in the README?
I don't think it's so important, but no problem to change it.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2017-05-29 10:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 7:47 versioning Karel Zak
2017-05-17 8:42 ` versioning Ruediger Meier
2017-05-17 8:47 ` versioning Ruediger Meier
2017-05-17 13:23 ` versioning Bernhard Voelker
2017-05-17 13:51 ` versioning Karel Zak
2017-05-17 15:04 ` versioning Karel Zak
2017-05-17 16:08 ` versioning Ruediger Meier
2017-05-17 17:36 ` versioning Bruce Dubbs
2017-05-17 19:07 ` versioning Ruediger Meier
2017-05-17 21:09 ` versioning Karel Zak
2017-05-18 9:29 ` versioning Sami Kerola
2017-05-18 10:36 ` versioning Karel Zak
2017-05-18 18:08 ` versioning J William Piggott
2017-05-18 19:56 ` versioning Karel Zak
2017-05-18 20:55 ` versioning Rüdiger Meier
2017-05-19 8:12 ` versioning Karel Zak
2017-05-19 19:00 ` versioning J William Piggott
2017-05-20 19:34 ` versioning Karel Zak
2017-05-22 21:37 ` versioning J William Piggott
2017-05-23 7:57 ` versioning Karel Zak
2017-05-23 8:05 ` versioning Karel Zak
2017-05-23 20:54 ` versioning J William Piggott
2017-05-24 10:02 ` versioning Ruediger Meier
2017-05-27 18:55 ` versioning J William Piggott
2017-05-29 10:22 ` Karel Zak [this message]
2017-05-18 10:43 ` versioning Ruediger Meier
2017-05-17 17:46 ` versioning J William Piggott
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170529102245.cbwndbup2nwbbcna@ws.net.home \
--to=kzak@redhat.com \
--cc=elseifthen@gmx.com \
--cc=sweet_f_a@gmx.de \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox