From: John Goerzen <jgoerzen@complete.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: git-rebase dirty index and email address bug?
Date: Sun, 2 Mar 2008 21:28:14 -0600 [thread overview]
Message-ID: <200803022128.14511.jgoerzen@complete.org> (raw)
In-Reply-To: <20080302072622.GB3935@coredump.intra.peff.net>
On Sunday 02 March 2008 1:26:22 am Jeff King wrote:
> I tried cloning the "mainline.git" repository you mentioned and doing a
> few simple tests, but was unable to reproduce. Can you make available
> the commits that you are trying to rebase?
That repo contains some local configuration and password information.
However, I would be happy to make it available to you or any other Git
developer privately. Could you contact me off-list if you'd like me to send
it to you? The .git directory in question is about 4.5MB, and I'd be happy
to email it.
-- John
next prev parent reply other threads:[~2008-03-03 3:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 20:40 git-rebase dirty index and email address bug? John Goerzen
2008-03-01 21:29 ` John Goerzen
2008-03-02 7:30 ` Jeff King
2008-03-02 13:44 ` John Goerzen
2008-03-02 7:26 ` Jeff King
2008-03-03 3:28 ` John Goerzen [this message]
2008-03-04 12:08 ` Jeff King
2008-03-04 15:22 ` John Goerzen
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=200803022128.14511.jgoerzen@complete.org \
--to=jgoerzen@complete.org \
--cc=git@vger.kernel.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 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).