From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] submitting a nice patch - quickguide for CVS users [was: Re:..]
Date: Mon, 5 Feb 2007 09:57:18 +0100 [thread overview]
Message-ID: <20070205085718.GD5399@aon.at> (raw)
In-Reply-To: <964506.40087.qm@web62003.mail.re1.yahoo.com>
On Sun, Feb 04, 2007 at 02:57:44PM -0800, Doug the RockRat wrote:
>Bernhard,
>If/when I submit patches, what form is most useful for
>you? If it is svn related, would you dump me a short
>command that I might use? I'm a CVS dog, and just
>haven't had time to see what it might take to move my
>CVS repo to svn.
If you create a new directory or add new files, you have to
$ svn add package/mything
resp.
$ svn add package/existing/newfile
To create a patch that we can apply with patch -p1, do
$ foo=$(basename $(pwd))
$ cd ..
$ svn diff --diff-cmd diff -x -rdup $foo > ~/mypatch.diff
$ mail -a ~/mypatch.diff -s "blah" buildroot at there
or the like, depending on your preferred MUA and svn defaults.
HTH,
parent reply other threads:[~2007-02-05 8:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <964506.40087.qm@web62003.mail.re1.yahoo.com>]
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=20070205085718.GD5399@aon.at \
--to=rep.dot.nop@gmail.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