From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Aguirre, Sergio" <saaguirre@ti.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [RFC] Procedures for git push
Date: Sat, 23 Jan 2010 13:37:08 -0200 [thread overview]
Message-ID: <4B5B17A4.6090201@redhat.com> (raw)
In-Reply-To: <A24693684029E5489D1D202277BE89445071D65E@dlee02.ent.ti.com>
Aguirre, Sergio wrote:
>>
>> At the email, please always send a summary of what's being send. Such summary is produced by
>> this commands:
>> git diff -M --stat --summary $ORIGIN `git branch |grep ^\*|cut -b3-`
>> echo
>> git log --pretty=short $ORIGIN..|git shortlog
>>
>> where $ORIGIN is the commit hash of the tree before your patches.
>
> Either that, or you can use following command:
>
> http://www.kernel.org/pub/software/scm/git/docs/git-request-pull.html
Good tip! I wrote the above commands based on my own submit script, that were written before
this command being added on -git ;)
I've updated the procedure to reflect this change.
In order to be easier for people to view the new version, I've added it at our wiki:
http://linuxtv.org/wiki/index.php/Maintaining_Git_trees
I did one or two cosmetic changes there also, and I added an useful information on how to submit
a fix patch that should also be applied at -stable.
For those that are sending contributions, I ask to not directly update the wiki (except if the
changes are cosmetic only) but send first an email about the proposed changes at this thread,
to allow a better review of the proposed changes.
Cheers,
Mauro
prev parent reply other threads:[~2010-01-23 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 14:33 [RFC] Procedures for git push Mauro Carvalho Chehab
2010-01-23 14:49 ` Aguirre, Sergio
2010-01-23 15:37 ` 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=4B5B17A4.6090201@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=saaguirre@ti.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.