From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2016, #01; Fri, 1)
Date: Sat, 2 Jul 2016 09:59:54 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1607020958210.12947@virtualbox> (raw)
In-Reply-To: <xmqqmvm0vry4.fsf@gitster.mtv.corp.google.com>
Hi,
On Fri, 1 Jul 2016, Junio C Hamano wrote:
> * jk/common-main-2.8 (2016-07-01) 5 commits
> - common-main: call git_setup_gettext()
> - common-main: call restore_sigpipe_to_default()
> - common-main: call sanitize_stdfds()
> - common-main: call git_extract_argv0_path()
> - add an extra level of indirection to main()
> (this branch is used by jk/common-main.)
>
> There are certain house-keeping tasks that need to be performed at
> the very beginning of any Git program, and programs that are not
> built-in commands had to do them exactly the same way as "git"
> potty does. It was easy to make mistakes in one-off standalone
> programs (like test helpers). A common "main()" function that
> calls cmd_main() of individual program has been introduced to
> make it harder to make mistakes.
To make it easier, I pushed my version of the patch series (including the
one required to be able to build with DEVELOPER=1) as 'common-main-maint'
to https://github.com/dscho/git.
Ciao,
Dscho
next prev parent reply other threads:[~2016-07-02 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 23:50 What's cooking in git.git (Jul 2016, #01; Fri, 1) Junio C Hamano
2016-07-02 7:59 ` Johannes Schindelin [this message]
2016-07-02 11:09 ` Johannes Schindelin
2016-07-06 14:41 ` Junio C Hamano
2016-07-06 15:32 ` Johannes Schindelin
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=alpine.DEB.2.20.1607020958210.12947@virtualbox \
--to=johannes.schindelin@gmx.de \
--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).