From: Jason Riedy <ejr@EECS•Berkeley.EDU>
To: Junio C Hamano <junkio@cox•net>
Cc: git@vger•kernel.org, Peter Eriksen <s022018@student•dtu.dk>
Subject: Re: [RFH] Solaris cloning woes...
Date: Tue, 04 Apr 2006 11:53:45 -0700 [thread overview]
Message-ID: <24378.1144176825@lotus.CS.Berkeley.EDU> (raw)
In-Reply-To: <7vu099916v.fsf@assigned-by-dhcp.cox.net>
And Junio C Hamano writes:
- Once this is confirmed to fix the problem on Solaris boxes, I'd
- like to include and do an 1.2.5, just in case OpenSolaris folks
- would want to play with it, and also put them in the "master"
- branch.
I haven't run into the problem since, but I almost never saw
it in the first place. Have you been able to trigger it
reliably? Maybe I'm "lucky" that my Sun's so slow...
Jason
prev parent reply other threads:[~2006-04-04 18:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 10:41 Solaris cloning woes partly diagnosed Junio C Hamano
2006-04-02 18:33 ` Linus Torvalds
2006-04-02 19:10 ` Jason Riedy
2006-04-02 19:22 ` Linus Torvalds
2006-04-02 19:18 ` Linus Torvalds
2006-04-02 19:52 ` Jason Riedy
2006-04-02 20:28 ` Linus Torvalds
2006-04-02 20:31 ` [PATCH 2/2] pack-objects: be incredibly anal about stdio semantics Linus Torvalds
2006-04-02 21:09 ` Junio C Hamano
2006-04-02 21:21 ` Linus Torvalds
2006-04-02 22:12 ` Jason Riedy
2006-04-02 22:58 ` Linus Torvalds
2006-04-02 22:29 ` [PATCH] Use sigaction and SA_RESTART in read-tree.c; add option in Makefile Jason Riedy
2006-04-03 1:02 ` Linus Torvalds
2006-04-03 4:20 ` Junio C Hamano
2006-04-03 4:40 ` Linus Torvalds
2006-04-03 3:06 ` Solaris cloning woes partly diagnosed Linus Torvalds
2006-04-04 18:21 ` H. Peter Anvin
2006-04-04 8:47 ` [RFH] Solaris cloning woes Junio C Hamano
2006-04-04 18:53 ` Jason Riedy [this message]
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=24378.1144176825@lotus.CS.Berkeley.EDU \
--to=ejr@eecs$(echo .)berkeley.edu \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
--cc=s022018@student$(echo .)dtu.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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