Aug 26, 2011
I have been doing proxy-maintainer now for a few people and I found
strange problem with fedpkg clog in relation to git
format-patch and git am.
If you have a changelog message like this:
I decided to try and fix fedpkg clog a bit. Given the previous changelog, now it creates git message like this:
If you have a changelog message like this:
* Mon Feb 28 2011 Stanislav Ochotnickyfedpkg commit -c would create git commit message like this:- 2.1.1-1 - Update to 2.1.1 - Update patch - Disable guice-eclipse for now
commit 22b5306036b6ef1022498b63e40324370ff7159b (HEAD, f15) Author: Stanislav OchotnickyThis works fine and mighty as long as you don't try to produce patch from this commit. Let's see what happens with git format-patch HEAD~1.AuthorDate: Fri Aug 26 11:45:54 2011 +0200 Update to 2.1.1 Update patch Disable guice-eclipse for now
$ head 0001-Update-to-2.1.1.patch f15 [22b5306] From 22b5306036b6ef1022498b63e40324370ff7159b Mon Sep 17 00:00:00 2001 From: Stanislav OchotnickyAfter adding this patch to repository using git am the line breaks would disappear. This is because git expects empty line after subject and description of the commit afterwards.Date: Fri, 26 Aug 2011 11:45:54 +0200 Subject: [PATCH] Update to 2.1.1 Update patch Disable guice-eclipse for now
I decided to try and fix fedpkg clog a bit. Given the previous changelog, now it creates git message like this:
commit 768964ce2145ef2b472fc5ef8781fb036d586b0e (HEAD, f15) Author: Stanislav OchotnickyThis means that git format-patch can do the right thing. I filed bug report for fedora-package so hopefully we can have this fixed sometime.AuthorDate: Fri Aug 26 11:57:20 2011 +0200 Update to 2.1.1 - Update patch - Disable guice-eclipse for now
0 comments:
Post a Comment