From: Uriel <uriell@binarydream.org>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] Patch updates and changes
Date: Fri, 23 Sep 2005 22:11:22 +0100 [thread overview]
Message-ID: <20050923211122.GC1342@server4.lensbuddy.com> (raw)
Just a FYI for people using patch(1), as I have seen various cases of
people creating more than one 'version' of a patch.
You can edit/remove/update patches until they are accepted/sorried/saved,
just go to /n/sources/patch/your-patch/ which is owned by you and edit
at will.
In case you have a new patch, rm -r works best to get rid of the old
patch and then replaced it with a new one of the same name using
patch/create.
If I got something wrong, russ will correct me :)
uriel
next reply other threads:[~2005-09-23 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 21:11 Uriel [this message]
2005-09-26 18:56 ` David Leimbach
2005-09-27 8:34 ` C H Forsyth
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=20050923211122.GC1342@server4.lensbuddy.com \
--to=uriell@binarydream.org \
--cc=9fans@cse.psu.edu \
/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).