From: Mauro Carvalho Chehab <maurochehab@gmail.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>,
Douglas Landgraf <dougsland@gmail.com>
Subject: Re: First -git merges
Date: Fri, 22 Jan 2010 19:55:24 -0200 [thread overview]
Message-ID: <4B5A1ECC.4000808@gmail.com> (raw)
In-Reply-To: <4B5A1D1E.2000701@redhat.com>
Mauro Carvalho Chehab wrote:
> As already announced, the patches are now being committed first on
> -git tree and then backported to -hg.
>
> In order to allow people to follow the patches that are being added
> at -git, I added a git hook that will send announcement emails when
> a patch is committed at:
> http://linuxtv.org/git/v4l-dvb.git
>
> Unfortunately, the first 3 or 4 git commits got lost while the hooks
> were being adjusted. Yet, as the first commits were small, it is easy
> to see the commit history at the gitweb interface.
>
> The backport to -hg will be done by Douglas.
Ah, I forgot to mention: if you're interested on seeing the commits, you
need to subscribe linuxtv-commits@linuxtv.org. In addition to the -hg
commits that were available there since the beginning of the -hg trees, you'll
be receiving also the -git commits. The -git commits are short: one message
per git push. The message will contain a summary of all patches added by
the git push.
I'll probably tweak the hook to produce a more customized message when I have
some time.
>
> Cheers,
> Mauro.
>
> -------- Mensagem original --------
> Assunto: [linuxtv-commits] [git:v4l-dvb] The merge of all V4L/DVB trees ready to upstream and linux-next branch, master, updated. v2.6.33-rc4-647-ga533f16
> Data: Fri, 22 Jan 2010 22:32:26 +0100
> De: Mauro Carvalho Chehab <linuxtv-commits-bounces@linuxtv.org>
> Para: linuxtv-commits@linuxtv.org
>
next prev parent reply other threads:[~2010-01-22 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 21:48 First -git merges Mauro Carvalho Chehab
2010-01-22 21:55 ` Mauro Carvalho Chehab [this message]
2010-01-22 22:03 ` Devin Heitmueller
2010-01-22 22:04 ` Devin Heitmueller
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=4B5A1ECC.4000808@gmail.com \
--to=maurochehab@gmail.com \
--cc=dougsland@gmail.com \
--cc=linux-media@vger.kernel.org \
/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