From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] util-linux: rename patches to follow the new name convention
Date: Wed, 10 Dec 2014 23:22:59 +0100 [thread overview]
Message-ID: <20141210222259.GK3926@free.fr> (raw)
In-Reply-To: <5488661E.10704@imgtec.com>
Vicente, All,
On 2014-12-10 15:26 +0000, Vicente Olivert Riera spake thusly:
> On 12/10/2014 03:21 PM, K?roly Kasza wrote:
> > Wouldn't be better to do all packages in one run of "git mv"-s?
Yes, there's a patch from Samuel doing that with a (Python!) script.
> I'm not sure, because there are lots of patches in the patchwork queue
> which may be touch some package-patches, so if you send a patch to
> rename all package-patches for all buildroot packages, there could be
> lots of patches that couldn't be applied as they are. I think it's
> better to fix one package at a time, but that's only my opinion, I could
> be wrong.
Well, except if one really want to bust his number of commits, there is
no reason to do so.
Yesterday during the Patchwork cleanup session, Peter agreed on using
Samuel's script to rename all patches in one go.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-12-10 22:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 13:14 [Buildroot] [PATCH 1/1] util-linux: rename patches to follow the new name convention Karoly Kasza
2014-12-10 15:11 ` Vicente Olivert Riera
2014-12-10 15:21 ` Károly Kasza
2014-12-10 15:26 ` Vicente Olivert Riera
2014-12-10 22:22 ` Yann E. MORIN [this message]
2014-12-10 20:23 ` 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=20141210222259.GK3926@free.fr \
--to=yann.morin.1998@free.fr \
--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