git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 6/6] git-gui: Update Japanese information

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 4, 2016, 01:20 UTC
Message-ID
<xmqqfuoc52q4.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<87mvilt4jg.fsf@red.patthoyts.tk>
Pat Thoyts <patthoyts@users.sourceforge.net> writes:
Show 6 quoted lines
> I've tried to merge in these branches as they appear in your version
> although I already had one patch on top of 0.20.0 for some time. I've
> tentatively pushed this up to http://github.com/patthoyts/git-gui as
> branch 'pu' with additional stuff on top of the patches you already
> have. If this looks ok to you I'll merge this to my master and send you
> a merge request to get it all synchronized.

Your 64c6b4c507 matches what I expected to see as the result of merging the above four topics on top of your 'master'. I have no opinion on the other topics that appear on top of it on the branch you pushed out, other than that I trust the maintainer of the subsystem and I'm fine to blindly pull them from you ;-)

I am not sure if f64a1a9311 ("git-gui: maintain backwards compatibility for merge syntax", 2016-10-04) makes any practical difference in the real world, though. You'd need to find somebody who grabs the newer version of git-gui that includes b5f325cb4a ("git-gui: stop using deprecated merge syntax", 2016-09-24), without having updated their copy of git-core for more than a year, given that 2.5.0 is from July last year. It would not hurt, but I am not sure if an extra invocation of "git version" is really worth it.

Thanks.
Previous: Pat Thoyts
Message 28 of 28 in “git-gui: The term unified for remote in Japanese”
  1. 1/6 git-gui: The term unified for remote in JapaneseSatoshi Yasushima, Sep 3, 2016
  2. 2/6 git-gui: The term unified for blame in JapaneseSatoshi Yasushima, Sep 3, 2016
  3. 4/6 git-gui: Add Japanese language codeSatoshi Yasushima, Sep 3, 2016
  4. 6/6 git-gui: Update Japanese informationSatoshi Yasushima, Sep 3, 2016
  5. 5/6 git-gui: Update Japanese translationSatoshi Yasushima, Sep 3, 2016
  6. Junio C HamanoSep 4, 2016
  7. Satoshi YasushimaSep 5, 2016
  8. Jakub NarębskiSep 4, 2016
  9. Satoshi YasushimaSep 5, 2016
  10. Satoshi YasushimaSep 5, 2016
  11. 1/6 git-gui: consistently use the same word for "remote" in JapaneseSatoshi Yasushima, Sep 6, 2016
  12. 2/6 git-gui: consistently use the same word for "blame" in JapaneseSatoshi Yasushima, Sep 6, 2016
  13. 5/6 git-gui: Update Japanese translationSatoshi Yasushima, Sep 6, 2016
  14. 4/6 git-gui: Add Japanese language codeSatoshi Yasushima, Sep 6, 2016
  15. 6/6 git-gui: Update Japanese informationSatoshi Yasushima, Sep 6, 2016
  16. Satoshi YasushimaSep 7, 2016
  17. Junio C HamanoSep 7, 2016
  18. git-gui, was Re: [PATCH v2 6/6] git-gui: Update Japanese informationJohannes Schindelin, Sep 8, 2016
  19. Junio C HamanoSep 8, 2016
  20. Vasco AlmeidaSep 20, 2016
  21. Junio C HamanoSep 21, 2016
  22. Junio C HamanoSep 26, 2016
  23. Satoshi YasushimaSep 8, 2016
  24. Pat ThoytsOct 3, 2016
  25. Junio C HamanoOct 3, 2016
  26. Junio C HamanoOct 3, 2016
  27. Pat ThoytsOct 3, 2016
  28. Junio C HamanoOct 4, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.