From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] python-pyusb: new package
Date: Mon, 28 Oct 2013 10:10:46 +0200 [thread overview]
Message-ID: <20131028081046.GA30640@sapphire.tkos.co.il> (raw)
In-Reply-To: <526E0E55.8060005@mind.be>
Hi Arnout,
On Mon, Oct 28, 2013 at 08:12:21AM +0100, Arnout Vandecappelle wrote:
> On 26/10/13 09:33, Wojciech Zabolotny wrote:
> >On Sat, Oct 26, 2013 at 1:41 AM, Arnout Vandecappelle <arnout@mind.be> wrote:
> >> Also, when sending an update, it is customary to add v2 to the subject
> >> so
> >>people can see which version is the latest one. You can do that by calling
> >>git send-email -v2 # Since git 1.8.x
> >>or
> >>git send-email --subject-prefix='PATCH v2'
> >
> >It seems, that the above should be applied to git format-patch, not
> >git send-email?
>
> You're right, but git send-email takes (almost) all of the options
> of git format-patch if you let it generate patches directly (e.g.
> with 'git send-email -1). Normally I don't bother with generating
> the patches separately and just mail them immediately - and I
> assumed that the rest of the world does the same :-).
How do you add patch version changelog then?
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2013-10-28 8:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 12:54 [Buildroot] [PATCH 1/1] Added pyusb as a package Wojciech M. Zabolotny
2013-10-25 15:26 ` Ryan Barnett
2013-10-25 16:50 ` Thomas De Schampheleire
2013-10-24 23:42 ` [Buildroot] [PATCH 1/1] Added jack2 as a package. Due to alignment errors on ARM platform, git sources are used Wojciech M. Zabolotny
2013-10-24 23:48 ` Wojciech Zabolotny
2013-10-25 23:36 ` [Buildroot] [PATCH 1/1] jack2: new package Wojciech M. Zabolotny
2013-10-27 17:10 ` Thomas Petazzoni
2013-10-27 19:50 ` [Buildroot] [PATCH v2 " Wojciech M. Zabolotny
2013-10-28 19:27 ` Thomas Petazzoni
2013-10-29 18:55 ` [Buildroot] [PATCH v3 " Wojciech M. Zabolotny
2013-10-29 19:34 ` Thomas Petazzoni
2013-10-30 0:00 ` Wojciech Zabolotny
2013-10-30 0:14 ` Thomas Petazzoni
2013-10-30 15:46 ` [Buildroot] [PATCH v4 " Wojciech M. Zabolotny
2014-03-07 23:10 ` Thomas Petazzoni
2013-10-25 23:15 ` [Buildroot] [PATCH 1/1] python-pyusb: " Wojciech M. Zabolotny
2013-10-25 23:41 ` Arnout Vandecappelle
2013-10-26 7:25 ` Wojciech M. Zabolotny
2013-10-26 7:35 ` [Buildroot] [PATCH v2 " Wojciech M. Zabolotny
2013-10-26 7:33 ` [Buildroot] [PATCH " Wojciech Zabolotny
2013-10-28 7:12 ` Arnout Vandecappelle
2013-10-28 8:10 ` Baruch Siach [this message]
2013-10-28 8:24 ` Arnout Vandecappelle
2013-10-28 8:40 ` Baruch Siach
2013-10-28 8:47 ` Arnout Vandecappelle
2013-10-28 9:03 ` Baruch Siach
-- strict thread matches above, loose matches on Subject: below --
2013-10-25 23:05 [Buildroot] [PATCH 1/1] Package python-pyusb added Wojciech M. Zabolotny
2013-10-25 23:09 ` Wojciech Zabolotny
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=20131028081046.GA30640@sapphire.tkos.co.il \
--to=baruch@tkos.co.il \
--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