git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Pat Thoyts <patthoyts@users.sourceforge.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Satoshi Yasushima" <s.yasushima@gmail.com>,
	git@vger.kernel.org, "Jakub Narębski" <jnareb@gmail.com>
Subject: Re: [PATCH v2 6/6] git-gui: Update Japanese information
Date: Mon, 03 Oct 2016 09:45:22 +0100	[thread overview]
Message-ID: <87int9x1lp.fsf@red.patthoyts.tk> (raw)
In-Reply-To: <xmqqk2enobol.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Wed, 07 Sep 2016 10:35:22 -0700")

Junio C Hamano <gitster@pobox.com> writes:

>"Satoshi Yasushima" <s.yasushima@gmail.com> writes:
>
>> There seems to be a cause in the following taboo.
>> Sure, PATCH 3/6 is little too great.
>> http://vger.kernel.org/majordomo-info.html#taboo
>>  >Taboo things to be done when discussing at VGER lists
>>   : (abbr.)
>>  > * Message size exceeding 100 000 characters causes blocking.
>>
>> To somehow.
>
>Since I received the patch directly bypassing vger, I queued it on
>gitgui-0.20.0 from Pat and tentatively merged it to my 'pu'.
>
>Pat, we haven't heard from you for a long time.  How would you want
>to proceed?  If you fetch from me and merge 52285c83 ("git-gui:
>update Japanese information", 2016-09-07), you'd get these six
>commits for po/ja.po and then we'd be in sync next time I pull from
>you.
>
>That is, if that ever happens--is git-gui pretty much in deep
>maintenance mode without anything more to do from your point of
>view?
>
>Thanks.
>

I'm just starting to catch up once again. hopefully I can be
a bit more reactive than recently. Merging 52285c83 looks fine. I'll
stick that onto the 0.20.0 head and see what else I can pick up on top.
There are a few from the git for windows set among others.
-- 
Pat Thoyts                            http://www.patthoyts.tk/
PGP fingerprint 2C 6E 98 07 2C 59 C8 97  10 CE 11 E6 04 E0 B9 DD

  parent reply	other threads:[~2016-10-03  8:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-03 14:43 [PATCH 1/6] git-gui: The term unified for remote in Japanese Satoshi Yasushima
2016-09-03 14:43 ` [PATCH 2/6] git-gui: The term unified for blame " Satoshi Yasushima
2016-09-03 14:43 ` [PATCH 4/6] git-gui: Add Japanese language code Satoshi Yasushima
2016-09-03 14:43 ` [PATCH 5/6] git-gui: Update Japanese translation Satoshi Yasushima
2016-09-03 14:43 ` [PATCH 6/6] git-gui: Update Japanese information Satoshi Yasushima
2016-09-04  6:54 ` [PATCH 1/6] git-gui: The term unified for remote in Japanese Junio C Hamano
2016-09-05 16:32   ` Satoshi Yasushima
2016-09-04 12:10 ` Jakub Narębski
2016-09-05 17:16   ` Satoshi Yasushima
2016-09-05 18:03     ` Satoshi Yasushima
2016-09-06 16:02 ` [PATCH v2 1/6] git-gui: consistently use the same word for "remote" " Satoshi Yasushima
2016-09-06 16:02   ` [PATCH v2 2/6] git-gui: consistently use the same word for "blame" " Satoshi Yasushima
2016-09-06 16:02   ` [PATCH v2 4/6] git-gui: Add Japanese language code Satoshi Yasushima
2016-09-06 16:02   ` [PATCH v2 5/6] git-gui: Update Japanese translation Satoshi Yasushima
2016-09-06 16:02   ` [PATCH v2 6/6] git-gui: Update Japanese information Satoshi Yasushima
2016-09-07 11:47     ` Satoshi Yasushima
2016-09-07 17:35       ` Junio C Hamano
2016-09-08  6:59         ` git-gui, was " Johannes Schindelin
2016-09-08 16:48           ` Junio C Hamano
2016-09-20 13:37             ` Vasco Almeida
2016-09-21 18:16               ` Junio C Hamano
2016-09-26 14:21                 ` Junio C Hamano
2016-09-08 12:55         ` Satoshi Yasushima
2016-10-03  8:45         ` Pat Thoyts [this message]
2016-10-03 16:18           ` Junio C Hamano
2016-10-03 19:31             ` Junio C Hamano
2016-10-03 23:07               ` Pat Thoyts
2016-10-04  1:20                 ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87int9x1lp.fsf@red.patthoyts.tk \
    --to=patthoyts@users.sourceforge.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=s.yasushima@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).