From: Lars Vogel <lars.vogel@vogella.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Lars Vogel <lars.vogel@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: [PATCH] Use "working tree" instead of "working directory" for git status
Date: Thu, 9 Jun 2016 20:21:03 +0200 [thread overview]
Message-ID: <CACA4a_Gzw5OXRc-ZaP78KOWW7nWzyN7KfWf_Gq_7vr+1HC-g0w@mail.gmail.com> (raw)
In-Reply-To: <CAPig+cR6j=L5P_i=D_6Q8Dfmu0jew9QDnRQTXjCJYQ9AUszz1g@mail.gmail.com>
Thanks updated patch on its way.
On Thu, Jun 9, 2016 at 7:55 PM, Eric Sunshine <sunshine@sunshineco.com> wrote:
> On Thu, Jun 9, 2016 at 1:46 PM, Lars Vogel <lars.vogel@gmail.com> wrote:
>> Working directory can be easily confused with the current directory.
>> In one of my patches I already updated the usage of working directory
>> with working tree for the man page but I noticed that git status also
>> uses this incorrect term.
>
> Missing sign-off.
>
>> ---
>> po/bg.po | 2 +-
>> po/ca.po | 2 +-
>> po/de.po | 2 +-
>> po/fr.po | 2 +-
>> po/git.pot | 2 +-
>> po/ko.po | 2 +-
>> po/ru.po | 2 +-
>> po/sv.po | 2 +-
>> po/vi.po | 2 +-
>> po/zh_CN.po | 2 +-
>> wt-status.c | 2 +-
>
> Don't bother updating the .po files; that's the job of the
> translators. Your patch should touch only wt-status.c.
>
>> 11 files changed, 11 insertions(+), 11 deletions(-)
--
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH
Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vogel@vogella.com, Web: http://www.vogella.com
next prev parent reply other threads:[~2016-06-09 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 17:46 [PATCH] Use "working tree" instead of "working directory" for git status Lars Vogel
2016-06-09 17:55 ` Eric Sunshine
2016-06-09 18:21 ` Lars Vogel [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-09 18:19 Lars Vogel
2016-06-09 19:46 ` Matthieu Moy
2016-06-09 19:59 ` 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=CACA4a_Gzw5OXRc-ZaP78KOWW7nWzyN7KfWf_Gq_7vr+1HC-g0w@mail.gmail.com \
--to=lars.vogel@vogella.com \
--cc=git@vger.kernel.org \
--cc=lars.vogel@gmail.com \
--cc=sunshine@sunshineco.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).