From: Greg KH <greg@kroah.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Andreas Ericsson <ae@op5.se>, git@vger.kernel.org
Subject: Re: Problems with using git
Date: Thu, 2 Mar 2006 15:58:24 -0800 [thread overview]
Message-ID: <20060302235824.GA13436@kroah.com> (raw)
In-Reply-To: <7vr75k5s4y.fsf@assigned-by-dhcp.cox.net>
On Thu, Mar 02, 2006 at 03:44:13PM -0800, Junio C Hamano wrote:
> Andreas Ericsson <ae@op5.se> writes:
>
> > Joseph Wakeling wrote:
> >> Thanks very much to all who offered advice on this. :-)
> >> Unfortunately openSUSE is somewhat out of sync not just with git but
> >> in
> >> libraries necessary to install the latest version (libcrypto.so.4,
> >> libssl.so.4). The openssl (0.9.7g-2.4) and openssl-devel (0.9.7g-2)
> >> packages don't contain these but rather contain libcrypto.so.0.9.7 and
> >> libssl.0.9.7. Just in case it's important to future git development.
> >
> > It might be useful for the openSuSE developers, but for git this is
> > totally irrelevant.
>
> True, but I had an impression that we had active developers in
> git community who are close to Suse, and I wonder why this
> hadn't come up earlier. Maybe our userbase and Suse's userbase
> do not overlap much?
Yes, some of us are quite close to SuSE :)
Anyway, the issue is that 10.0 was released about 6 months ago, and
contains the version of git at that time. The latest development tree,
and the latest public betas contain 1.1.3. If you think this should be
newer, I can easily go poke the proper people...
thanks,
greg k-h
next prev parent reply other threads:[~2006-03-02 23:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 0:25 Problems with using git Joseph Wakeling
2006-03-02 0:52 ` Linus Torvalds
2006-03-02 1:24 ` Andreas Ericsson
2006-03-02 13:52 ` Joseph Wakeling
2006-03-02 13:59 ` Andreas Ericsson
2006-03-02 23:44 ` Junio C Hamano
2006-03-02 23:58 ` Greg KH [this message]
2006-03-04 10:56 ` Mark Wooding
2006-03-04 22:25 ` Greg KH
2006-03-08 2:16 ` Greg KH
2006-03-02 23:21 ` Greg KH
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=20060302235824.GA13436@kroah.com \
--to=greg@kroah.com \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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 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).