Lines Matching +refs:info +refs:get +refs:reply

46 definitive reference for them.  Please check the gcc info pages (`info
155     happen, and what to do if you want to get a change into one of these
358 Fixing bugs is one of the best ways to get merits among other developers,
362 Check the MAINTAINERS file where bugs for that subsystem get reported to; often
367 kernel get filed there.
406 get pretty large. Don't remove anybody from the CC: list without a good
407 reason, or don't reply only to the list address. Get used to receiving the
412 keep the "John Kernelhacker wrote ...:" lines at the top of your reply, and
423 own patch by yourself. If that doesn't work, get your mail program fixed
448 again, sometimes things get lost in the huge volume.
513 order to get ideas across properly on mailing lists, so it is
565 unfinished work. Therefore it is good to get early in the process to
566 get feedback to improve your work, but also keep your changes in small
567 chunks that they may get already accepted, even when your whole task is