smi...@icebubble.org writes: > used in Plan 9/plan9port. Now that I'm getting into development, I'd
Well, I've been hacking on P9P for a bit, rolled up a patch, and noticed that the patch contains edits to the shebang (#!) lines for the shell scripts in the development tree. I presume they're the changes made by the moveplan9.sh script. What's the conventional way to omit these shebang edits when committing code? I could moveplan9.sh the #! paths back to /usr/local/plan9. But then the development environment would be broken. I could run moveplan9.sh before and after each commit; but that would be annoying and get old real fast. Moving the tree to the real /usr/local/plan9 would risk breaking the existing installed (and working) P9P while development is underway. I was thinking I could up wrap the #! edits into a patch, and apply that patch before and after every commit, but that would be about equally as tedious as having to run moveplan9.sh over and over again. Any ideas? What's the customary way to do this? -- +---------------------------------------------------------------+ |Smiley <smi...@icebubble.org> PGP key ID: BC549F8B | |Fingerprint: 9329 DB4A 30F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B| +---------------------------------------------------------------+
