From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Vincent McIntyre <vincent.mcintyre@gmail.com>
Cc: Jarod Wilson <jarod@wilsonet.com>,
Martin Dauskardt <martin.dauskardt@gmx.de>,
linux-media@vger.kernel.org
Subject: Re: difference mchehab/new_build.git to media_build.git ?
Date: Mon, 10 Jan 2011 10:55:38 -0200 [thread overview]
Message-ID: <4D2B01CA.9090209@redhat.com> (raw)
In-Reply-To: <AANLkTinrYg=gD3DXu8kXM83hk7mnEFGUY-7gpUegBj5i@mail.gmail.com>
Em 09-01-2011 02:01, Vincent McIntyre escreveu:
>> There's no difference. It started out at mchehab/new_build.git, then got
>> moved
>> to media_build.git, but there's a symlink in place to keep from breaking
>> things
>> for people who originally checked it out at the old location.
>>
>> The move essentially promoted it from "something Mauro's tinkering with" to
>> "something generally useful for a wider audience". And its also being worked
>> on
>> by more people than just Mauro now (myself included).
>
> Thanks for clarifying this. Doesn't this justify a one-line NEWS item?
> I can understand not wanting to mention it while still experimental, but now...
I was actually waiting for someone to manifest as being the maintainer of it,
before doing that announcement, but it is probably fine to add it.
I can add it later, but I'm a little busy this week. So, if someone could prepare
me the news text (in HTML, if possible), this would help a lot.
Cheers,
Mauro
next prev parent reply other threads:[~2011-01-10 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 17:47 difference mchehab/new_build.git to media_build.git ? Martin Dauskardt
2011-01-08 17:50 ` Jarod Wilson
2011-01-09 4:01 ` Vincent McIntyre
2011-01-10 12:55 ` Mauro Carvalho Chehab [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-09 18:23 CityK
2011-01-10 12:52 ` Mauro Carvalho Chehab
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=4D2B01CA.9090209@redhat.com \
--to=mchehab@redhat.com \
--cc=jarod@wilsonet.com \
--cc=linux-media@vger.kernel.org \
--cc=martin.dauskardt@gmx.de \
--cc=vincent.mcintyre@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox