From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: ASoC updates for v3.8
Date: Thu, 29 Nov 2012 17:44:45 +0000 [thread overview]
Message-ID: <20121129174445.GP32691@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <s5hsj7snxc1.wl%tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 517 bytes --]
On Thu, Nov 29, 2012 at 06:16:46PM +0100, Takashi Iwai wrote:
> Mark Brown wrote:
> > It's an accurate reflection of
> > what's happening.
> Yes, and this reveals something ugly really happened.
> Using gitk (or any other GUI) is a very fundamental workflow for
> normal developers. We mustn't mess it up.
I don't see it as ugly to be honest - it's no worse for me than any
other gitk log, they're all unreadable in the merge window. The massive
pile of branches just gets splattered even further over the map.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-11-29 17:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 16:10 ASoC updates for v3.8 Mark Brown
2012-11-29 16:30 ` Takashi Iwai
2012-11-29 16:44 ` Mark Brown
2012-11-29 17:05 ` Takashi Iwai
2012-11-29 17:10 ` Mark Brown
2012-11-29 17:16 ` Takashi Iwai
2012-11-29 17:44 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-17 13:14 Mark Brown
2012-12-17 14:09 ` Takashi Iwai
2012-12-17 14:25 ` Mark Brown
2012-12-17 14:45 ` Takashi Iwai
2013-01-26 7:40 Mark Brown
2013-01-27 9:28 ` Takashi Iwai
2013-02-06 13:22 Mark Brown
2013-02-06 13:33 ` Takashi Iwai
2013-02-06 13:35 ` Mark Brown
2013-02-06 13:43 ` Takashi Iwai
2013-02-06 14:13 ` Mark Brown
2013-02-06 14:18 ` Takashi Iwai
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=20121129174445.GP32691@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=tiwai@suse.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