git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Keller, Jacob E" <jacob.e.keller@intel.com>
To: "gitster@pobox.com" <gitster@pobox.com>
Cc: "j6t@kdbg.org" <j6t@kdbg.org>,
	"git@vger.kernel.org" <git@vger.kernel.org>,
	"sortie@maxsi.org" <sortie@maxsi.org>
Subject: Re: What's cooking in git.git (Sep 2014, #01; Tue, 2)
Date: Wed, 3 Sep 2014 19:30:19 +0000	[thread overview]
Message-ID: <1409772619.28694.0.camel@jekeller-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <xmqqoauwy0lz.fsf@gitster.dls.corp.google.com>

On Wed, 2014-09-03 at 12:18 -0700, Junio C Hamano wrote:
> Johannes Sixt <j6t@kdbg.org> writes:
> 
> > But IMHO, this topic goes in a wrong direction. "Avoid deprecated
> > interfaces" is way overrated. It would be preferable (IMHO) to implement
> > setitimer() in compat/ for systems that don't have it.
> 
> I think I agree.
> 
> Adding compat/setitimer.c that implements git_setitimer() in terms
> of whatever is available on the platform and #define calls to
> setitimer() away to git_setitimer() would be a lot less intrusive
> change than the series posted.
> 
> Thanks.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

I suppose overall this makes more sense :) That shouldn't be difficult
to do.

Regards,
Jake

  reply	other threads:[~2014-09-03 19:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 22:06 What's cooking in git.git (Sep 2014, #01; Tue, 2) Junio C Hamano
2014-09-03  6:27 ` Johannes Sixt
2014-09-03 18:45   ` Torsten Bögershausen
2014-09-03 19:18   ` Junio C Hamano
2014-09-03 19:30     ` Keller, Jacob E [this message]
2014-09-04 13:46 ` Duy Nguyen
2014-09-04 16:51   ` Junio C Hamano
2014-09-04 17:14     ` Junio C Hamano
2014-09-04 17:25       ` Junio C Hamano
2014-09-05  1:18       ` Duy Nguyen
2014-09-05  0:47     ` Duy Nguyen
2015-03-26 13:46 ` Tommy38

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1409772619.28694.0.camel@jekeller-desk1.amr.corp.intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.org \
    --cc=sortie@maxsi.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).