From: Jakub Narebski <jnareb@gmail.com>
To: Sebastien Douche <sdouche@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git list <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git 1.7.5
Date: Mon, 25 Apr 2011 03:32:45 -0700 (PDT) [thread overview]
Message-ID: <m3oc3uwrja.fsf@localhost.localdomain> (raw)
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
next prev parent reply other threads:[~2011-04-25 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 20:31 [ANNOUNCE] Git 1.7.5 Junio C Hamano
2011-04-25 0:00 ` Sebastien Douche
2011-04-25 1:07 ` Sebastien Douche
2011-04-25 10:32 ` Jakub Narebski [this message]
2011-04-25 10:57 ` Ævar Arnfjörð Bjarmason
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=m3oc3uwrja.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sdouche@gmail.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).