From: anikey <arty.anikey@gmail.com>
To: git@vger.kernel.org
Subject: Git Bug - diff in commit message.
Date: Thu, 8 Sep 2011 07:49:13 -0700 (PDT) [thread overview]
Message-ID: <1315493353942-6772145.post@n2.nabble.com> (raw)
Hi, peops. I'm pretty much sure that's a bug.
What I did was putting git diff (i needed to tell people that for my changes
to start working they needed to aplly message-inline patch to some code
which was not under git) in commit message. Like adding:
diff --git a/app/controllers/settings_controller.rb
b/app/controllers/settings_controller.rb
index 937da74..0e8440d 100644
--- a/app/controllers/settings_controller.rb
+++ b/app/controllers/settings_controller.rb
@@ -42,7 +42,7 @@ class SettingsController < ApplicationController
end
def snmp_mibs
- render layout: 'ext3'
+ render layout: 'ext3_2'
end
def cfg_auth_keys(auth_type=:all)
though the commit itself didn't contain that change. So while `git rebase
some_branch_name` I started getting:
First, rewinding head to replay your work on top of it...
Applying: My cool patch.
fatal: sha1 information is lacking or useless
(app/controllers/settings_controller.rb).
Repository lacks necessary blobs to fall back on 3-way merge.
Cannot fall back to three-way merge.
Patch failed at 0001 My cool patch.
When you have resolved this problem run "git rebase --continue".
If you would prefer to skip this patch, instead run "git rebase --skip".
To restore the original branch and stop rebasing run "git rebase --abort".
I wasn't able to figure out what was wrong for a very long time, when things
came to my mind.
Thanks.
--
View this message in context: http://git.661346.n2.nabble.com/Git-Bug-diff-in-commit-message-tp6772145p6772145.html
Sent from the git mailing list archive at Nabble.com.
next reply other threads:[~2011-09-08 14:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 14:49 anikey [this message]
2011-09-08 16:26 ` Git Bug - diff in commit message Michael Witten
2011-09-09 0:56 ` Thomas Rast
2011-09-09 6:14 ` Johannes Sixt
2011-09-09 16:00 ` Junio C Hamano
2011-10-11 23:00 ` Junio C Hamano
2011-10-24 23:24 ` Martin von Zweigbergk
2011-10-25 14:11 ` Junio C Hamano
2011-09-08 17:27 ` Junio C Hamano
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=1315493353942-6772145.post@n2.nabble.com \
--to=arty.anikey@gmail.com \
--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).