From: Jakub Narebski <jnareb@gmail.com>
Date: Mon, 25 Apr 2011 10:32:45 GMT
Subject: Re: [ANNOUNCE] Git 1.7.5
Message-ID: <m3oc3uwrja.fsf@localhost.localdomain>
In-Reply-To: <BANLkTikhkCDZ5Crw+KGWBprXd6qoFOH8kg@mail.gmail.com>

Sebastien Douche <sdouche@gmail.com> writes:

> On Sun, Apr 24, 2011 at 22:31, Junio C Hamano <gitster@pobox.com> wrote:
> > The latest feature release Git 1.7.5 is available at the usual
> > places:
> 
> Great! Thank you for this new release. Btw, I've some questions, sorry
> if these seem like frivolous or stupid questions.
> 
> >  * The codebase is getting prepared for i18n/l10n; no translated
> >    strings nor translation mechanism in the code yet, but the strings
> >    are being marked for l10n.
> 
> Where are pot files for Git and Gitweb?

Actually only programs in C and shell scripts are prepared for
translation.  Currently there is no infrastructure for translating
scripts implemented in Perl... including Git.pm module and gitweb.
 
> >  * "git checkout --detach <commit>" is a more user friendly synonym for
> >    "git checkout <commit>^0".
> 
> What is the interest?

What do you mean?  "git checkout <commit>^0" is quite cryptic way to
detach HEAD, and requires deeper knowledge of Git... though I am not
sure why somebody not knowledgeable in Git might want to detach HEAD
explicitly at given commmit / branch.

> >  * "git checkout" performed on detached HEAD gives a warning and
> >    advice when the commit being left behind will become unreachable from
> >    any branch or tag.
> 
> No sure to understand, it's not already the case?

It is reworked to show warning and advice only when it is really
needed.

-- 
Jakub Narebski
Poland
ShadeHawk on #git