From: Guillaume Quintard <guillaume.quintard@gmail.com>
To: "Sup-talk@rubyforge.org" <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Crash, bad index, and ensuing misery
Date: Sat, 3 Oct 2009 23:54:28 +0200 [thread overview]
Message-ID: <1e5fdab70910031454n28c57ae5m1f33f10f4e4acaab@mail.gmail.com> (raw)
In-Reply-To: <1254605615-sup-5636@zyrg.net>
On Sat, Oct 3, 2009 at 11:39 PM, Rich Lane <rlane@club.cc.cmu.edu> wrote:
> Please post the output of "git log --pretty=oneline 'origin/next^'.."
>
here you go
80789d873ac555bb1979f7734e95f104d848007e Merge branch 'next' of
git://gitorious.org/sup/mainline into next
0eee0973223b625b66e30c196ccd45d2f7bf358b Merge branch 'master' into next
93b5552730c10e2a352bd33f5ee98800bcd8679e more release-script updates
d1eabf9cb21940b933464ab3efc25df3c1a5f7e1 Merge branch 'next' of
git://gitorious.org/sup/mainline into next
df96980d0573cf91742a8f9ae5e8a49366d338b8 Merge branch 'next' of
git://gitorious.org/sup/mainline into next
a6dcb02dda7dd8bb1742890d460b1b0abfc28454 Merge branch 'next' of
git://gitorious.org/sup/mainline into next
823148627f554fbf5a7fb13379567276eeee14c7 Merge branch 'next' of
git://gitorious.org/sup/mainline into next
40ecc407a8aacf16d7f9f104501311cfd1fb2eb7 Revert "Merge branch
'after-add-message-hook' into next"
--
Guillaume
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-10-03 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 20:04 Guillaume Quintard
2009-10-03 20:17 ` Rich Lane
2009-10-03 21:06 ` Guillaume Quintard
2009-10-03 21:39 ` Rich Lane
2009-10-03 21:54 ` Guillaume Quintard [this message]
2009-10-06 12:40 ` Olly Betts
2009-10-06 13:10 ` Guillaume Quintard
2009-10-03 22:25 ` Rich Lane
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=1e5fdab70910031454n28c57ae5m1f33f10f4e4acaab@mail.gmail.com \
--to=guillaume.quintard@gmail.com \
--cc=sup-talk@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox