From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] What is the proper procedure to commit a patch?
Date: Fri, 6 Jul 2007 14:35:32 +0200 [thread overview]
Message-ID: <006201c7bfd9$de0f46a0$dcc4af0a@atmel.com> (raw)
Now, when I have access, I would like to understand the proper
procedure to add patches.
After checking out and applying a patch, I can do:
svn commit -F <file>
with <file> containing a log message.
or
svn commit -m "log message"
I tried a real simple patch first and after the commit,
the svn server automatically sent out a mail with the change,
adding the log message.
The patches I'd like to add are mainly:
* BSP patch ,discussed and approved by Eric.
* moving package/customize to topdir and rename "local", also discussed before
* Support for AT91 boot monitors
Dataflashboot
AT91-Bootstrap
U-boot
Generate U-Boot initialization scripts
* Add AVR32 support.
* A few extra packages.
* Update mtdutils (which is really old)
* Clean up the linux support (move into a separate dir in package)
* Bump versions on a number of packages which has disappeared from their download location.
(dash, rmp, l2tp, mpfr,mrouted, openntpd, portage, pppd,udev)
* Add TARGET_CFLAGS to all packages not having this
Would like to know if they lack TARGET_CFLAGS for a reason.
(acpid,berkleydb, hdparm, iostat,ltp-testsuite,memtester,netkitbase,
procps, python, sysklogd, tinyx,udhcp)
* Introduce concept of distributions (did not do any work there yet though)
--------------
Both the version bump and TARGET_CFLAGS lists are a month old, so
maybe the svn already is updated.
Is it OK to bump version if something disappears from internet, or do we need a review.
Sometimes you find new versions of a package, Is it OK to bump the version
without previous review by peers?
Anything else to think about (except golden rule: do not break the build)?
Best Regards
Ulf Samuelsson ulf at atmel.com
Atmel Nordic AB
Mail: Box 2033, 174 02 Sundbyberg, Sweden
Visit: Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22 Fax +46 (8) 441 54 29
GSM +46 (706) 22 44 57
Technical support when I am not available:
AT90 AVR Applications Group: mailto:avr at atmel.com
AT91 ARM Applications Group: mailto:at91support at atmel.com
AVR32 Applications Group mailto:avr32 at atmel.com
http://www.avrfreaks.net/; http://avr32linux.org/
http://www.at91.com/ ; ftp://at91dist:distrib at 81.80.104.162/
next reply other threads:[~2007-07-06 12:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 12:35 Ulf Samuelsson [this message]
2007-07-06 15:26 ` [Buildroot] What is the proper procedure to commit a patch? Bernhard Fischer
2007-07-06 15:36 ` Ulf Samuelsson
2007-07-07 10:12 ` Bernhard Fischer
2007-07-07 11:16 ` Ulf Samuelsson
2007-07-07 12:35 ` Bernhard Fischer
2007-07-07 13:46 ` Ulf Samuelsson
2007-07-06 15:55 ` Steven J. Hill
2007-07-06 21:10 ` Ulf Samuelsson
2007-07-07 10:06 ` [Buildroot] $(TARGET_CONFIGURE_OPTS) $(MAKE) vs $(MAKE) $(TARGET_CONFIGURE_OPTS) Ulf Samuelsson
2007-07-07 13:01 ` Bernhard Fischer
2007-07-07 16:06 ` Ulf Samuelsson
2007-07-07 17:29 ` Bernhard Fischer
2007-07-07 19:37 ` Ulf Samuelsson
2007-07-07 21:16 ` Bernhard Fischer
2007-07-07 22:49 ` Ulf Samuelsson
2007-07-09 8:25 ` Bernhard Fischer
2007-07-09 9:21 ` Bernhard Fischer
2007-07-09 12:20 ` Steven J. Hill
2007-07-09 13:41 ` Julien Letessier
2007-07-09 13:08 ` Ulf Samuelsson
2007-07-09 16:33 ` Bernhard Fischer
2007-07-10 11:51 ` Julien Letessier
2007-07-10 18:24 ` Bernhard Fischer
2007-07-07 10:21 ` [Buildroot] What is the proper procedure to commit a patch? Bernhard Fischer
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='006201c7bfd9$de0f46a0$dcc4af0a@atmel.com' \
--to=ulf@atmel.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 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.