From: smiley@icebubble.org
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9/plan9port coding conventions
Date: Mon, 16 Jan 2012 22:50:22 +0000 [thread overview]
Message-ID: <86mx9n6z4h.fsf@cmarib.ramside> (raw)
In-Reply-To: <86vcoif5f4.fsf@cmarib.ramside> (smiley@icebubble.org's message of "Wed, 11 Jan 2012 18:41:19 +0000")
smiley@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 <smiley@icebubble.org> PGP key ID: BC549F8B |
|Fingerprint: 9329 DB4A 30F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B|
+---------------------------------------------------------------+
next prev parent reply other threads:[~2012-01-16 22:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 18:41 smiley
2012-01-11 18:53 ` Richard Miller
2012-01-12 20:20 ` Yaroslav
2012-01-11 19:01 ` Jeremy Jackins
2012-01-11 20:37 ` Russ Cox
2012-01-11 20:45 ` erik quanstrom
2012-01-11 21:20 ` John Floren
2012-01-11 21:25 ` Russ Cox
2012-01-11 23:00 ` Iruatã Souza
2012-01-11 23:57 ` John Stalker
2012-01-12 1:33 ` Skip Tavakkolian
[not found] ` <CAJSxfmJdLV8NMJgMFPcqCP+=ZGe8k2U=PcdkpexwUzbcL442+Q@mail.gmail.c>
2012-01-12 2:53 ` erik quanstrom
2012-01-12 15:18 ` Comeau At9Fans
2012-01-12 17:56 ` Christian Neukirchen
2012-01-12 23:07 ` Skip Tavakkolian
2012-01-13 14:55 ` Andrés Domínguez
2012-01-16 10:02 ` faif
2012-01-16 11:04 ` John Stalker
2012-01-16 22:50 ` smiley [this message]
2012-01-16 22:57 ` andrey mirtchovski
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=86mx9n6z4h.fsf@cmarib.ramside \
--to=smiley@icebubble.org \
--cc=9fans@9fans.net \
/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).