All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vadim Evard <v.e.evard@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH v2] configure: silence pkg-config's check for curses
Date: Mon, 21 Jan 2013 01:36:54 +0400	[thread overview]
Message-ID: <50FC6376.2050903@gmail.com> (raw)
In-Reply-To: <20130118140619.GA28079@stefanha-thinkpad.redhat.com>

Thank you!

By the way (sorry if this was discussed before and is a strong decision) 
I'd say e-mail based workflow is of course very flexible - and very very 
novice-unfriendly. Dash, I had to learn git commands I'd never use in my 
usual workflow with local or Github repos. And, well, I was not very 
good with that. 10 ways with 10 options in each. You all saw my previous 
patch mail with "fubar" header and no signed-off-by string.

Is there a reason you (team) don't use e.g. Github at least for trivial 
patches?

Regards,
Vadim

  reply	other threads:[~2013-01-20 21:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 13:48 [Qemu-trivial] [Qemu-devel] [PATCH v2] configure: silence pkg-config's check for curses Vadim Evard
2013-01-18 13:48 ` [Qemu-devel] [Qemu-trivial] " Vadim Evard
2013-01-18 14:06 ` [Qemu-trivial] [Qemu-devel] " Stefan Hajnoczi
2013-01-18 14:06   ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2013-01-20 21:36   ` Vadim Evard [this message]
2013-01-21 10:54     ` Stefan Hajnoczi
  -- strict thread matches above, loose matches on Subject: below --
2013-01-15 23:52 [Qemu-trivial] [Qemu-devel] [PATCH] configure: silencing " Vadim Evard
2013-01-16 14:54 ` Anthony Liguori
2013-01-16 20:17   ` [Qemu-devel] [Qemu-trivial] [PATCH v2] configure: silence " Vadim Evard
2013-01-17 20:01     ` Anthony Liguori

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=50FC6376.2050903@gmail.com \
    --to=v.e.evard@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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.