On Fri, Jan 13, 2012 at 1:39 PM, Dave Page <dp...@pgadmin.org> wrote: > On Fri, Jan 13, 2012 at 1:29 PM, Simon Riggs <si...@2ndquadrant.com> wrote: >> On Fri, Jan 13, 2012 at 1:22 PM, Robert Haas <rh...@postgresql.org> wrote: >> >>> Typo fix. >> >> Hmm, how strange. I fixed that bug immediately before commit, so must >> have skipped a step while committing. > > If you modify a file after git-adding it, you have to re-add it before > committing. Possible cause?
No, dumber than that. I compiled a new version, just skipped the bit where I updated the new patch version, so the old one just got applied. I keep separate dev and write repositories and use patches to move between them. Which gives me less chance of committing dev code accidentally (like I just did). Is there a better way? -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
