Re: [26771] trunk/dports/devel/git-core
On Jul 6, 2007, at 16:41, source_changes@macosforge.org wrote:
Revision: 26771 http://trac.macosforge.org/projects/macports/changeset/26771 Author: mgrimes@macports.org Date: 2007-07-06 14:41:49 -0700 (Fri, 06 Jul 2007)
Log Message: ----------- Update to git-core 1.5.2.3
- Add p5-error (Fix #12240) - Refresh and rename patch files to literal naming conventions instead of functional. - Add darwin_9 variant to workaround ticket #12245. - whitespace fixes
It would be better if you could commit whitespace changes separately from functional changes. This makes it much easier to tell by glancing at a diff what functional changes have been made in a given revision.
On Sat, 7 Jul 2007 22:14:06 -0500, Ryan Schmidt wrote:
On Jul 6, 2007, at 16:41, source_changes@macosforge.org wrote:
Revision: 26771 http://trac.macosforge.org/projects/macports/changeset/26771 Author: mgrimes@macports.org Date: 2007-07-06 14:41:49 -0700 (Fri, 06 Jul 2007)
Log Message: ----------- Update to git-core 1.5.2.3
- Add p5-error (Fix #12240) - Refresh and rename patch files to literal naming conventions instead of functional. - Add darwin_9 variant to workaround ticket #12245. - whitespace fixes
It would be better if you could commit whitespace changes separately from functional changes. This makes it much easier to tell by glancing at a diff what functional changes have been made in a given revision.
Thanks for the heads up! Yup went over this with the maintainer -- since I'm decentralized I have a non-standard excuse: it was late when I committed it to my local git branch and I forgot that it was bundled when I pushed it up to svn the next day. Unfortunately with subversion I can't go back and amend (re-edit metadata and update the tree) the commit without svnadmin voodoo... Indeed git has spoiled me. I will check my local branches more carefully before pushing upstream. Cheers! Mark Grimes, MacPorts http://www.macports.org/
participants (2)
-
Mark Grimes
-
Ryan Schmidt