From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Simon Paillard <spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: git repo: more updates before each final tag ?
Date: Sat, 08 Jun 2013 05:47:27 +0200 [thread overview]
Message-ID: <51B2A94F.5050601@gmail.com> (raw)
In-Reply-To: <20130603195635.GN3511-8MNqHwMchPhGJ/Ie3qa20WD2FQJk+8+b@public.gmane.org>
Hi Simon,
On 06/03/13 21:56, Simon Paillard wrote:
> Hi Michael,
>
> Would it be possible for you to push commits gradually, i.e. not to soon before
> the final release / tag, but soon after your local commit ?
Yep, sorry -- it's been a while since the last push (but it will still be
a while before a release). I've now done a push a couple of days back.
> It would allow us:
> * to spot any typos or groff issues, that are far easier to fix upstream
> than patch in the manpages package or in translations (like we do in
> perkamon-fr).
> * to have more time to prepare translations, in order to reach timely
> synchronized releases between the english and the translated (here french)
> version.
>
> Thanks a lot :)
No problem. Bug me any time when you see I'm slow to do a push.
Cheers,
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-06-08 3:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 19:56 git repo: more updates before each final tag ? Simon Paillard
[not found] ` <20130603195635.GN3511-8MNqHwMchPhGJ/Ie3qa20WD2FQJk+8+b@public.gmane.org>
2013-06-08 3:47 ` Michael Kerrisk [this message]
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=51B2A94F.5050601@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.