From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Kyungmin Park <kmpark@infradead.org>,
linux-media@vger.kernel.org, kernel@pengutronix.de,
Pawel Osciak <pawel@osciak.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Hans Verkuil <hverkuil@xs4all.nl>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Jeremy Kerr <jk@ozlabs.org>
Subject: Re: [PATCH] [media] V4L/videobuf2-memops: use pr_debug for debug messages
Date: Fri, 03 Jun 2011 16:56:12 -0300 [thread overview]
Message-ID: <4DE93C5C.5050301@infradead.org> (raw)
In-Reply-To: <20110603195022.GF9907@pengutronix.de>
Em 03-06-2011 16:50, Uwe Kleine-König escreveu:
>
>> Fortunately, as the patches on this branch are meant to go to v3.1,
>> I just renamed the branch to staging/for_v3.1, keeping the wrong patch
>> at the old branch. This way, the need of rebasing was avoided.
> I don't get what you mean here. Which merge is broken? Just in case you
> didn't know, git push -f should be able to overwrite the remote branch,
> with all the downside that brings that with it.
A git push -f will cause troubles on all clones of the media tree.
Cheers,
Mauro
prev parent reply other threads:[~2011-06-03 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 20:19 [PATCH] [media] V4L/videobuf2-memops: use pr_debug for debug messages Uwe Kleine-König
2011-06-02 0:50 ` Kyungmin Park
2011-06-02 1:34 ` Mauro Carvalho Chehab
2011-06-02 5:56 ` Marek Szyprowski
2011-06-02 11:06 ` Mauro Carvalho Chehab
2011-06-03 7:39 ` Uwe Kleine-König
2011-06-03 15:39 ` Mauro Carvalho Chehab
2011-06-03 19:50 ` Uwe Kleine-König
2011-06-03 19:56 ` Mauro Carvalho Chehab [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=4DE93C5C.5050301@infradead.org \
--to=mchehab@infradead.org \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=jk@ozlabs.org \
--cc=kernel@pengutronix.de \
--cc=kmpark@infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=pawel@osciak.com \
--cc=u.kleine-koenig@pengutronix.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