Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bluez5_utils: bumped version number to 5.25
Date: Sat, 22 Nov 2014 17:16:15 +0100	[thread overview]
Message-ID: <20141122171615.7eb18494@free-electrons.com> (raw)
In-Reply-To: <546F6FCB.1090101@imgtec.com>

Dear Vicente Olivert Riera,

On Fri, 21 Nov 2014 17:00:59 +0000, Vicente Olivert Riera wrote:

> Another one. When you create the patch using "git format-patch", before
> sending it, please edit the patch using your favourite text editor and
> add the version number in the "Subject" line. Here is an example using
> your own patch:
> 
> Subject: [PATCH v2] bluez5_utils: bumped version number to 5.25

Just a quick comment: there's no need to fire up a text editor to do
this. Just do:

	git format-patch --subject-prefix="PATCHv2"

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-11-22 16:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 16:36 [Buildroot] [PATCH] bluez5_utils: bumped version number to 5.25 Jaap Crezee
2014-11-21 17:00 ` Vicente Olivert Riera
2014-11-22 16:16   ` Thomas Petazzoni [this message]
2014-11-23  5:40     ` Baruch Siach
2014-11-24 10:04     ` Vicente Olivert Riera
2014-11-22 18:00 ` Thomas Petazzoni
2014-11-26 21:56   ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2014-11-23  0:12 Peter Seiderer
2014-11-26 22:01 ` Thomas Petazzoni
2014-11-30 14:37 Jaap Crezee
2014-11-30 14:40 ` Baruch Siach
2014-11-30 14:43   ` Jaap Crezee
2014-11-30 14:59     ` Baruch Siach
2014-12-02  7:19       ` Jaap Crezee
2014-12-07 23:03     ` Thomas Petazzoni

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=20141122171615.7eb18494@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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