All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] Added new menu item to specify a custom port for /etc/inittab
Date: Wed, 29 Sep 2010 10:36:43 +0200	[thread overview]
Message-ID: <4CA2FA9B.8060405@visionsystems.de> (raw)
In-Reply-To: <20100928192629.1717d83c@surf>

> Would people cry/complain if instead of the following patch we simply
> replace the TARGET_GENERIC_GETTY_PORT parameter by a single free-form
> text-field ?

I wouldn't ;-) Let's make it this way.

Yegor

      reply	other threads:[~2010-09-29  8:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24  7:35 [Buildroot] [PATCH 0/4] /etc/inittab stuff and device creation stuff Yegor Yefremov
     [not found] ` <4C9C54FC.4040609@visionsystems.de>
2010-09-24  7:37   ` [Buildroot] [PATCH 2/4] Enable terminal type configuration for /etc/inittab Yegor Yefremov
2010-09-24  7:38     ` [Buildroot] [PATCH 3/4] Create menu entry to select device creation method Yegor Yefremov
2010-09-24  7:39       ` [Buildroot] [PATCH 4/4] Add network scripting folders to fs/skeleton Yegor Yefremov
2010-09-28 17:40         ` Thomas Petazzoni
2010-11-22 18:47         ` Thomas Petazzoni
2010-09-28 17:35       ` [Buildroot] [PATCH 3/4] Create menu entry to select device creation method Thomas Petazzoni
2010-09-29 12:18         ` Yegor Yefremov
2010-09-30 12:57           ` Yegor Yefremov
2010-11-22 18:47             ` Thomas Petazzoni
2010-09-28 17:28     ` [Buildroot] [PATCH 2/4] Enable terminal type configuration for /etc/inittab Thomas Petazzoni
2010-09-29  8:31       ` Yegor Yefremov
2010-09-27  8:53 ` [Buildroot] [PATCH 1/4] Added new menu item to specify a custom port " Yegor Yefremov
2010-09-28 17:26   ` Thomas Petazzoni
2010-09-29  8:36     ` Yegor Yefremov [this message]

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=4CA2FA9B.8060405@visionsystems.de \
    --to=yegor_sub1@visionsystems.de \
    --cc=buildroot@busybox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.