From: Rod Boyce <buildroot@teamboyce.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Ogg and Vorbis patch part 2.1
Date: Fri, 01 Jun 2007 11:28:33 +0100 [thread overview]
Message-ID: <465FF4D1.20709@teamboyce.co.uk> (raw)
In-Reply-To: <20070531214638.GE12010@aon.at>
Bernhard Fischer wrote:
> Thanks for the update, but please see below..
>
>> Regards,
>> Rod Boyce
>>
>>
>
>
> you want --exclude='*~'
> Alternatively, a simple "svn diff > ~/mypatch.diff" should do the right
> thing.
>
>
Bernhard,
If you know a way to get svn diff to work the same way as diff -uN does
then I am listening. I have tried passing -N to svn diff but without
success so that is why I am using just diff. I have even tried 'svn
diff --diff-cmd `which diff` -x "-uN --recursive"' but it still does not
show new files in the diff output. As for me when I just do svn diff I
only get changes to files that are on SVN I don't get my new changes.
Attached are all the other suggested changes as these mostly obvious.
But gnuconfig needs updating and it is gettign in the way of my diffs
now and I have to exclude yet another directory.
Regards,
Rod Boyce
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libogg-libvorbis.patch
Type: text/x-patch
Size: 7979 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20070601/7894b917/attachment.bin
next prev parent reply other threads:[~2007-06-01 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 13:22 [Buildroot] Ogg and Vorbis patch Rod Boyce
2007-05-29 20:25 ` Bernhard Fischer
2007-05-31 18:54 ` [Buildroot] Ogg and Vorbis patch part 2 Rod Boyce
2007-05-31 21:46 ` Bernhard Fischer
2007-06-01 10:28 ` Rod Boyce [this message]
2007-06-01 11:33 ` [Buildroot] Ogg and Vorbis patch part 2.1 Peter Korsgaard
2007-06-01 17:49 ` [Buildroot] SVN diff was " Rod Boyce
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=465FF4D1.20709@teamboyce.co.uk \
--to=buildroot@teamboyce.co.uk \
--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