From: Karel Zak <kzak@redhat.com>
To: kerolasa@gmail.com
Cc: Benno Schulenberg <bensberg@justemail.net>,
util-linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 02/11] docs: improve some wordings on the man page of wipefs
Date: Tue, 6 Jan 2015 14:30:44 +0100 [thread overview]
Message-ID: <20150106133044.GI18528@x2.net.home> (raw)
In-Reply-To: <CAG27Bk02NPEZukdCbVDTugCcqRk7ieg+S+85q0yJRkPdDPmBfQ@mail.gmail.com>
On Tue, Jan 06, 2015 at 01:26:44PM +0000, Sami Kerola wrote:
> On 6 January 2015 at 13:13, Karel Zak <kzak@redhat.com> wrote:
> > On Mon, Dec 29, 2014 at 11:16:57AM +0100, Benno Schulenberg wrote:
> >> misc-utils/wipefs.8 | 33 +++++++++++++++++----------------
> >> 1 files changed, 17 insertions(+), 16 deletions(-)
> >
> > Grrr... I see you resent the patches :-)
> >
> > Please, please, use --in-reply-to= or at least "V2" in subject
> > next time when you re-send patches. I thought it's another set of
> > patches.
> >
> > Or ideally use github to keep your patches up to date in some task
> > specific branch, then I can merge all by one git-pull command. In
> > this case is enough to send to mailing list info that you have
> > updated the patches. (Ask Sami for more details, he uses this way :-)
>
> I rather send update to Documentation/howto-contribute.txt how to sent
> remote branch requests. The description will be technically OK, and
> Benno will end up fixing the engrish again ;-)
It would be nice to have description for all the work flow and how to
use git in this case (which git commands and how) for people who are
not familiar with git and github.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2015-01-06 13:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 10:16 [PATCH 02/11] docs: improve some wordings on the man page of wipefs Benno Schulenberg
2014-12-29 10:16 ` [PATCH 03/11] ipcs: in usage show resource option as nonoptional when used with -i Benno Schulenberg
2014-12-29 10:16 ` [PATCH 04/11] ipcrm: gettextize the command synopsis of the usage text Benno Schulenberg
2014-12-29 10:17 ` [PATCH 05/11] docs: restore the alternative form of setarch in its man page Benno Schulenberg
2014-12-29 10:17 ` [PATCH 06/11] setarch: make the usage synopsis comprehensible for translators Benno Schulenberg
2014-12-29 10:17 ` [PATCH 07/11] textual: list the options of setarch in a more alphabetical order Benno Schulenberg
2014-12-29 10:17 ` [PATCH 08/11] colcrt: slice up the usage text for ease of translation Benno Schulenberg
2014-12-29 10:17 ` [PATCH 09/11] look: " Benno Schulenberg
2014-12-29 10:17 ` [PATCH 10/11] tailf: " Benno Schulenberg
2014-12-29 10:17 ` [PATCH 11/11] ipc*: use customary fputs() instead of fprintf() with the usage macros Benno Schulenberg
2015-01-06 13:13 ` [PATCH 02/11] docs: improve some wordings on the man page of wipefs Karel Zak
2015-01-06 13:26 ` Sami Kerola
2015-01-06 13:30 ` Karel Zak [this message]
2015-01-06 22:51 ` Sami Kerola
2015-01-06 21:08 ` Benno Schulenberg
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=20150106133044.GI18528@x2.net.home \
--to=kzak@redhat.com \
--cc=bensberg@justemail.net \
--cc=kerolasa@gmail.com \
--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