From: Rod Boyce <buildroot@teamboyce.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] SVN diff was Ogg and Vorbis patch part 2.1
Date: Fri, 01 Jun 2007 18:49:19 +0100 [thread overview]
Message-ID: <46605C1F.5050405@teamboyce.co.uk> (raw)
In-Reply-To: <87fy5bj4d7.fsf@sleipner.barco.com>
Peter Korsgaard wrote:
> Hi,
>
> RB> If you know a way to get svn diff to work the same way as diff -uN
> RB> does then I am listening. I have tried passing -N to svn diff but
> RB> without success so that is why I am using just diff. I have even
> RB> tried 'svn diff --diff-cmd `which diff` -x "-uN --recursive"' but
> RB> it still does not show new files in the diff output. As for me
> RB> when I just do svn diff I only get changes to files that are on
> RB> SVN I don't get my new changes.
>
> Just svn add them before diffing
Peter,
Thank you for this tip I was looking at svn diff as a waste of space.
Regards,
Rod Boyce
prev parent reply other threads:[~2007-06-01 17:49 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 ` [Buildroot] Ogg and Vorbis patch part 2.1 Rod Boyce
2007-06-01 11:33 ` Peter Korsgaard
2007-06-01 17:49 ` Rod Boyce [this message]
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=46605C1F.5050405@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