git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mike Ralphson" <mike.ralphson@gmail.com>
To: "Boyd Lynn Gerber" <gerberb@zenez.com>
Cc: "Git List" <git@vger.kernel.org>, "Junio C Hamano" <gitster@pobox.com>
Subject: Re: Bug/problem with 1.6.0 on UnixWare
Date: Thu, 21 Aug 2008 13:41:07 +0100	[thread overview]
Message-ID: <e2b179460808210541lfd7dcaeoea8554a2a76f8825@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0808210610440.29396@xenau.zenez.com>

2008/8/21 Boyd Lynn Gerber <gerberb@zenez.com>:
> Yep, that sounds about right.  It has bitten me on the 12 platforms, I
> submitted to get git working on them.  I will look at reverting it.
>
> I just tried to get this working and now I am being flooded with emails
> from people that are trying git for the first time, and asking...
>
> How I could your recommend such a broken SCM?  I told them to got back to
> the 1.5.X but being new to git and then not being able to build and use it
> is causing a lot of flack.  I am getting emails now about my recommending
> git, as it is broken.  I should not have announce to the various lists
> about how great git is and that they should dump their older SCM's in
> favor of git.  Really bad timing on my part.  I just hope these people
> will give git an other try.

If it's possible, you might want to look at automatically building and
running the git testsuite on some or all of your SCO etc platforms.
You're very welcome to push tags describing the state of the build and
tests to http://repo.or.cz/w/git/gitbuild.git - there's a few scripts
there in a side branch.

Personally, I'd like it if Junio could check to see if the 'satellite'
platforms are happily building and passing the last rc before he tags
a final release (with no additional code changes in it!), but that may
be too much of the tail wagging the dog.

Even though 1.6 builds and passes here, I probably won't push it out
in my environment until 1.6.0.2 or so.

Mike

  reply	other threads:[~2008-08-21 12:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21 11:25 Bug/problem with 1.6.0 on UnixWare Boyd Lynn Gerber
2008-08-21 11:35 ` Mike Ralphson
2008-08-21 12:18   ` Boyd Lynn Gerber
2008-08-21 12:41     ` Mike Ralphson [this message]
2008-08-21 13:08       ` Jeff King
2008-08-21 14:38         ` Mike Ralphson
2008-08-21 20:45           ` Jeff King
2008-08-22  7:58             ` Mike Ralphson

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=e2b179460808210541lfd7dcaeoea8554a2a76f8825@mail.gmail.com \
    --to=mike.ralphson@gmail.com \
    --cc=gerberb@zenez.com \
    --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).