From: Vikram Narayanan <vikram186@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 4/4] patman: Handle creation of patman config
Date: Tue, 01 May 2012 08:44:22 +0530 [thread overview]
Message-ID: <4F9F550E.1010602@gmail.com> (raw)
In-Reply-To: <CAPnjgZ1eKvWWY14JNhNFj=4nYH9p7NsYdaUs62HcBZFYNCrGFg@mail.gmail.com>
On 4/30/2012 11:07 PM, Simon Glass wrote:
> Hi Vikram,
>
> On Fri, Apr 27, 2012 at 9:39 AM, Vikram Narayanan <vikram186@gmail.com
> <mailto:vikram186@gmail.com>> wrote:
>
>
> patman shouts when it couldn't find a $(HOME)/.config/patman file.
> Handle it in a sane way by creating a new one for the user.
> It looks for a user.name <http://user.name> and user.email in the
> global .gitconfig
> file, waits for the user input if it can't find those.
>
> Signed-off-by: Vikram Narayanan <vikram186@gmail.com
> <mailto:vikram186@gmail.com>>
> Cc: Simon Glass <sjg at chromium.org <mailto:sjg@chromium.org>>
>
>
> Acked-by: Simon Glass <sjg at chromium.org <mailto:sjg@chromium.org>>
>
> In terms of changing the config file to ~/.patman, this could actually
> be a subsequent patch if you like. But there are a few nits below if you
> re-issue.
>
I feel that can be dealt in a separate patch which follows this. For the
few nits, I'll send a v3 _only_ for this patch and not for the whole
series as the other two are ACK'ed and one is decided not to be ACK'ed.
Thanks,
Vikram
prev parent reply other threads:[~2012-05-01 3:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 16:39 [U-Boot] [PATCH v2 4/4] patman: Handle creation of patman config Vikram Narayanan
2012-04-30 8:44 ` Wolfgang Denk
2012-04-30 13:37 ` Vikram Narayanan
2012-04-30 17:10 ` Simon Glass
2012-04-30 17:37 ` Simon Glass
2012-05-01 3:14 ` Vikram Narayanan [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=4F9F550E.1010602@gmail.com \
--to=vikram186@gmail.com \
--cc=u-boot@lists.denx.de \
/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