From: Daniele Salvatore Albano <info@daccii.it>
To: buildroot@busybox.net
Subject: [Buildroot] [Off Topic] Sending Patches from Git
Date: Wed, 30 Mar 2011 11:12:52 +0200 [thread overview]
Message-ID: <4D92F414.1010804@daccii.it> (raw)
Hi,
i know that this is absolutely off topic to this mailing list, but i
would send some patches (related to php, cryptoloop, freeswitch and more).
I've commited some code to my local git repository, checkouted from
buildroot git server, how i can "extract" patches without being mad? For
the previous patches i re-checkouted buildroot sources, manually diffed
with my code, splitted in chunks and re-commited to extract patches to send.
All these operations requires hours of time making patch sending hard
and complex.
There is a better way to do?
Best Regards,
Daniele
--
____________________________________________________________
|
Daniele Salvatore Albano | web site:
IT Consultant | http://www.itechcon.it
Website Design and Development |
Software Engineer and Developer | e-mail:
Linux Servers SetUp And Administration | info at itechcon.it
Embedded Network Solutions | info at daccii.it
Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute in
questo messaggio sono riservate ed a uso esclusivo del destinatario.
Qualora il messaggio in parola Le fosse pervenuto per errore, La
invitiamo ad eliminarlo senza copiarlo e a non inoltrarlo a terzi,
dandocene gentilmente comunicazione. Grazie.
Pursuant to Legislative Decree No. 196/2003, you are hereby informed
that this message contains confidential information intended only for
the use of the addressee. If you are not the addressee, and have
received this message by mistake, please delete it and immediately
notify us. You may not copy or disseminate this message to anyone. Thank
you.
next reply other threads:[~2011-03-30 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 9:12 Daniele Salvatore Albano [this message]
2011-03-30 9:23 ` [Buildroot] [Off Topic] Sending Patches from Git Mike Frysinger
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=4D92F414.1010804@daccii.it \
--to=info@daccii.it \
--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