From: Zeeshan Qureshi <zeeshan@zqureshi.in>
To: git@vger.kernel.org
Subject: Re: Git commit behaving strangely
Date: Wed, 21 Jul 2010 00:01:10 -0400 [thread overview]
Message-ID: <AANLkTin9cGW77iqXR63XPmJkft_RXjw5nLkdmUNIjgmA@mail.gmail.com> (raw)
In-Reply-To: <20100721030608.GA25992@burratino>
Hello Jonathan,
The problem seems to be with the Blastwave git package (it 1.6.x) on Solaris.
I tried reproducing it on 2 different linux machines (both running git
1.7) and I couldn't reproduce it.
I will do it again when I get to work tomorrow (i don't have remote
access to the workstation) and post the results.
Thanks,
Zeeshan
next prev parent reply other threads:[~2010-07-21 4:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 2:28 Git commit behaving strangely Zeeshan Qureshi
2010-07-21 3:06 ` Jonathan Nieder
2010-07-21 4:01 ` Zeeshan Qureshi [this message]
[not found] ` <AANLkTikYoNEQpotpfdVci4WSUc1GMNnM9y0OqXJb7Fzu@mail.gmail.com>
[not found] ` <20100721050558.GA15273@burratino>
2010-07-22 13:48 ` Zeeshan Qureshi
2010-07-22 16:28 ` Jonathan Nieder
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=AANLkTin9cGW77iqXR63XPmJkft_RXjw5nLkdmUNIjgmA@mail.gmail.com \
--to=zeeshan@zqureshi.in \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).