From: Erik Faye-Lund <kusmabite@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2010, #01; Tue, 9)
Date: Tue, 9 Nov 2010 23:25:24 +0100 [thread overview]
Message-ID: <AANLkTikbA0qYKZ8BtDgKA8KXKu3d_JtUGVF9d6HFUgJC@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinwdFvR4AV9nR=9sVuMYYZHMn4C7RQ0wneX6Ys+@mail.gmail.com>
On Tue, Nov 9, 2010 at 11:21 PM, Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> On Tue, Nov 9, 2010 at 23:17, Erik Faye-Lund <kusmabite@gmail.com> wrote:
>> On Tue, Nov 9, 2010 at 8:53 PM, Junio C Hamano <gitster@pobox.com> wrote:
>>> * ab/i18n (2010-10-07) 161 commits
>>> - po/de.po: complete German translation
>>> - po/sv.po: add Swedish translation
>>> - gettextize: git-bisect bisect_next_check "You need to" message
>> <...>
>>> - tests: use test_cmp instead of piping to diff(1)
>>> - t7004-tag.sh: re-arrange git tag comment for clarity
>>>
>>> Will merge to 'next' to see what happens; it is getting ridiculously
>>> painful to keep re-resolving the conflicts with other topics in flight,
>>> even with the help with rerere.
>>
>> Hmmm, this is a bit more annoying IMO - this currently breaks in
>> msysgit, due to lack of gettext and NO_GETTEXT not working properly.
>> Ævar is aware of this
>> (AANLkTiny+NmXew6UxjNMO+o75=CxxWm9iVRMRxs0LyTJ@mail.gmail.com), but
>> haven't fixed it yet. I do have the patches needed to get a gettext in
>> msysgit, so it's not a very big deal to me. But are you sure that this
>> makes this series ready for 'next'?
>
> I hear ya. I'm hoping to get around to fixing all this stuff before it
> lands in "next".
>
Good to hear :)
> Also going to look at your gettext patches to see if there's anything
> there that needs
> to be made part of the series.
>
My "gettext-patches" are patches for msysgit (the development
environment used to build Git for Windows) to build and install
gettext. They're not patches against git.git, so I doubt they are
useful to outside of msysgit.git.
next prev parent reply other threads:[~2010-11-09 22:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 19:53 What's cooking in git.git (Nov 2010, #01; Tue, 9) Junio C Hamano
2010-11-09 20:11 ` Ævar Arnfjörð Bjarmason
2010-11-09 20:19 ` Matthieu Moy
2010-11-09 20:29 ` Drew Northup
2010-11-09 20:38 ` Jonathan Nieder
2010-11-09 21:38 ` Jakub Narebski
2010-11-11 17:21 ` Junio C Hamano
2010-11-11 23:53 ` Jakub Narebski
2010-11-09 21:46 ` Johan Herland
2010-11-09 22:11 ` Jeff King
2010-11-09 22:17 ` Erik Faye-Lund
2010-11-09 22:21 ` Ævar Arnfjörð Bjarmason
2010-11-09 22:25 ` Erik Faye-Lund [this message]
2010-11-09 22:27 ` Ævar Arnfjörð Bjarmason
2010-11-10 20:35 ` Yann Dirson
2010-11-11 12:26 ` Nguyen Thai Ngoc Duy
2010-11-11 14:28 ` Nguyen Thai Ngoc Duy
2010-11-14 13:02 ` [PATCH] use persistent memory for rejected paths Clemens Buchacher
2010-11-15 18:31 ` Junio C Hamano
2010-11-15 19:02 ` Clemens Buchacher
2010-11-15 19:03 ` Matthieu Moy
2010-11-15 19:41 ` Clemens Buchacher
2010-11-15 19:52 ` [PATCH v2] " Clemens Buchacher
2010-11-16 16:41 ` Matthieu Moy
2010-11-15 23:05 ` [PATCH] " Junio C Hamano
2010-11-15 23:30 ` Clemens Buchacher
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=AANLkTikbA0qYKZ8BtDgKA8KXKu3d_JtUGVF9d6HFUgJC@mail.gmail.com \
--to=kusmabite@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).