git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Michele Ballabio <barra_cuda@katamail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitk: move es.po where it belongs
Date: Mon, 19 May 2008 09:50:21 +1000	[thread overview]
Message-ID: <18480.49341.345744.262423@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <200805171916.31106.barra_cuda@katamail.com>

Michele Ballabio writes:

> Signed-off-by: Michele Ballabio <barra_cuda@katamail.com>
> ---
>  {gitk-git/po => po}/es.po |    0 
>  1 files changed, 0 insertions(+), 0 deletions(-)
>  rename {gitk-git/po => po}/es.po (100%)
> 
> diff --git a/gitk-git/po/es.po b/po/es.po
> similarity index 100%
> rename from gitk-git/po/es.po
> rename to po/es.po

Thanks, applied.

Paul.

      reply	other threads:[~2008-05-18 23:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-17 17:16 [PATCH] gitk: move es.po where it belongs Michele Ballabio
2008-05-18 23:50 ` Paul Mackerras [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=18480.49341.345744.262423@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=barra_cuda@katamail.com \
    --cc=git@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;
as well as URLs for NNTP newsgroup(s).