All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Nicolas Pitre <nico@cam.org>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH, resent] fix openssl headers conflicting with custom SHA1 implementations
Date: Wed, 1 Oct 2008 09:39:52 -0700	[thread overview]
Message-ID: <20081001163952.GJ21310@spearce.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0810011222090.3635@xanadu.home>

Nicolas Pitre <nico@cam.org> wrote:
> On Wed, 1 Oct 2008, Shawn O. Pearce wrote:
> > Jeff King <peff@peff.net> wrote:
> > > On Wed, Oct 01, 2008 at 08:54:58AM -0700, Shawn O. Pearce wrote:
> > > 
> > > > I think its easy enough to just rename our SHA_CTX and SHA_*
> > > > functions to something more git specific.  Since its mostly a global
> > > 
> > > I think that is the cleanest and simplest solution. As for merging pain,
> > > I think Junio would generally do a mechanical change like this as the
> > > first thing after a release. However, in this case, I think we might
> > > want it sooner if the conflict is causing breakage.
> > 
> > Oh, yea, that's probably true.  But with ARM broken according to
> > Nico I'd almost just want this fixed in the upcoming 1.6.1 release.
> 
> > Its simple enough to do.  We can even do something like this during
> > the transition period until right before the 1.6.1 final:
> 
> Because it's easy to do then I'd do it sooner than later.

Nico, are you going to write a patch for this?  If not I'll do it
myself later today or tomorrow morning.  I don't mind doing it,
I just don't want to duplicate work with you.  I've got too much
else going on to waste my time that way.

Of course I'm wasting time on this email... ;-)

-- 
Shawn.

  reply	other threads:[~2008-10-01 16:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 20:22 [PATCH, resent] fix openssl headers conflicting with custom SHA1 implementations Nicolas Pitre
2008-09-30 20:39 ` Shawn O. Pearce
2008-09-30 20:46   ` Nicolas Pitre
2008-09-30 20:51     ` Shawn O. Pearce
2008-10-01  3:47       ` Jeff King
2008-10-01 15:54         ` Shawn O. Pearce
2008-10-01 16:04           ` Jeff King
2008-10-01 16:10             ` Shawn O. Pearce
2008-10-01 16:35               ` Nicolas Pitre
2008-10-01 16:39                 ` Shawn O. Pearce [this message]
2008-10-01 18:05                   ` [PATCH v2] " Nicolas Pitre

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=20081001163952.GJ21310@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=peff@peff.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.