search for: interdiff

I've resolved the conflicts between the xen-unstable svn tree's patchset and xen-unstable 16319 (which was the tip a few days ago). The result is below, as the output of `svn diff' - so a series of interdiffs, unfortunately. Also, I noticed that after installing the resulting packages, it wasn't able to correctly select the xen-unstable tools; instead, it fell back to the default. In my installation I fixed this by making a symlink /usr/lib/xen-3.2 -> xen-unstable. Perhaps this should be made...

...d be a security issue? Many thanks in advance Martin [1] http://www.debian-interix.net/ [2] http://www.suacommunity.com/forum/tm.aspx?m=4663&mpage=1&key=setuser&#7061 [3] http://www.debian-interix.net/debian-interix/pool/unreleased35/main/o/openssh/openssh_4.7p1-9_4.7p1-9+interix.2.interdiff.gz

...ed "make-fedora-img.pl" from the already modified project(s) to the next project, and used "git add -p" to review and stage the changes I wanted. And then I compared the candidate patch to the actual commit in the other (already modified) project(s), effectively looking at "interdiff"s. There was at least one surprise that way: see virt-v2v commit fd7cd0c0fd22 / guestfs-tools commit 21e051c0c846. We don't have the same in libguestfs (in fact I'd not been aware of guestfs-tools commit 21e051c0c846!), and now I didn't want to change the size of the Root LV -- the...

...in debian/patches are an output which is best ignored. Instead, look at the history of the actual upstream files. > The relationship between patches and changes in them is not stored in > git history because every time things end up in new unrelated commits. It is true that you can't interdiff patches so easily. IME one probably wants to do that rarely anyway. > The history of the current master branch, doing the packaging from 4.8 > via 4.9 and 4.10 to 4.11 and all the changes still does fit on your > screen. I like this. I can just read back what I did and why. > > S...

...e patch below makes tinc use it (patch against > 1.1-pre11). Basically the patch turns the handle_incoming_vpn_data > variables into arrays (of size 1 when recvmmsg is not available, and > thus compiled the same as before), and makes the code index into the > arrays. You may want to use interdiff -w /dev/null patch to better see > what changes the patch makes. > > With this patch, I saw the non-ciphered bandwidth achieved over direct > ethernet improve from 680Mbps to 800Mbps (or conversely, reduce the CPU > usage for the same bandwidth). That's great! It would be good...

For the series: Reviewed-by: Richard W.M. Jones <rjones at redhat.com> BTW it's usually possible to cherry pick across git repos, eg: $ git fetch ../libguestfs $ git cherry-pick -x <hash> Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical

...rom() at a time. The patch below makes tinc use it (patch against 1.1-pre11). Basically the patch turns the handle_incoming_vpn_data variables into arrays (of size 1 when recvmmsg is not available, and thus compiled the same as before), and makes the code index into the arrays. You may want to use interdiff -w /dev/null patch to better see what changes the patch makes. With this patch, I saw the non-ciphered bandwidth achieved over direct ethernet improve from 680Mbps to 800Mbps (or conversely, reduce the CPU usage for the same bandwidth). More is yet to come: I'll have a look at extending the t...

Package: xen-3 Version: 3.1.1-1 See the transcript below, where I * dpkg-source -x debian/xen-3_3.1.1-1.dsc * add an entry to debian/changelog at the top * run dpkg-buildpackage, which fails I installed the build-dependencies on sid and lenny and the path it's looking for doesn't exist there either. Thanks, Ian. mariner:d> dpkg-source -x ../debian/xen-3_3.1.1-1.dsc gpg:

...ch/x86/kernel/macros.S I absolutely agree that this needs to be resolved in v4.20. So I did the 1-9 reverts manually myself as well, because I think the first commit should be reverted fully to get as close to the starting point as possible (we are late in the cycle) - and came to the attached interdiff between your series and mine. Does this approach look OK to you, or did I miss something? Thanks, Ingo =============> entry/calling.h | 2 - include/asm/jump_label.h | 50 ++++++++++++++++++++++++++++++++++------------- 2 files changed, 38 insertions(+), 14 deletions(-) dif...

This series reverts the in-kernel workarounds for inlining issues. The commit description of 77b0bf55bc67 mentioned "We also hope that GCC will eventually get fixed,..." Now, GCC provides a solution. https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html explains the new "asm inline" syntax. The performance issue will be eventually solved. [About Code cleanups] I know Nadam

This series reverts the in-kernel workarounds for inlining issues. The commit description of 77b0bf55bc67 mentioned "We also hope that GCC will eventually get fixed,..." Now, GCC provides a solution. https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html explains the new "asm inline" syntax. The performance issue will be eventually solved. [About Code cleanups] I know Nadam

...e patch below makes tinc use it (patch against > 1.1-pre11). Basically the patch turns the handle_incoming_vpn_data > variables into arrays (of size 1 when recvmmsg is not available, and > thus compiled the same as before), and makes the code index into the > arrays. You may want to use interdiff -w /dev/null patch to better see > what changes the patch makes. > > With this patch, I saw the non-ciphered bandwidth achieved over direct > ethernet improve from 680Mbps to 800Mbps (or conversely, reduce the CPU > usage for the same bandwidth). > > More is yet to come: I'...

...# if __GNUC__ >= 2 > > > # define __func__ __FUNCTION__ > > > # else > > > # define __func__ "<unknown>" > > > # endif > > > #endif > > > > > > > > > > > > Here is the interdiff wrt recent version as posted to the list, and the > > > full patch: > > > > [...] > > > > Arnaud, Arjen, > > > > So what would we do about this patch? > > > > I've tried to address the issues you've raised, and to describe my > &gt...

Summary: I have tried the packaging-only repo and I really don't like it at all. I don't know how anyone copes with this - such hard work! IMO we should switch to git-debrebase. (As an alternative, if you don't trust git-debrebase because it's my own tool, gbp pq would be better, too, even though it's not as good as git-debrebase.) Particularly, now that we have more people

Hello, I have a problem shutting down a domU with xen-4.1.2, which doesn''t terminate the corresponding blktap2 process, since one (other) VM uses a image file, which contains spaces in its file name. /var/log/xen/xend-debug.log has the following information: Unhandled exception in thread started by Traceback (most recent call last): File

http://bugzilla.mindrot.org/show_bug.cgi?id=413 ------- Additional Comments From dtucker at zip.com.au 2005-01-24 14:27 ------- Created an attachment (id=782) --> (http://bugzilla.mindrot.org/attachment.cgi?id=782&action=view) forward-bind.sh: regression test for binding port forwards to addresses Current limitations of test: - no testing of IPv6 - no testing of backwards compat

...changes to the host's SCSI target implementation. This includes all the changes suggested by Hannes, Rusty and Ben in reply to the previous version of the draft. Here is the lyx version. The PDF version is at http://people.redhat.com/pbonzini/virtio-spec.pdf and the text version of the spec (interdiff from v1) is in a reply to this message. --- virtio-spec.lyx.saved 2011-11-29 14:00:59.782659120 +0100 +++ virtio-spec.lyx 2011-12-05 14:02:41.946266491 +0100 @@ -56,6 +56,7 @@ \html_math_output 0 \html_css_as_file 0 \html_be_strict false +\author 1531152142 "pbonzini" \end_header...

...changes to the host's SCSI target implementation. This includes all the changes suggested by Hannes, Rusty and Ben in reply to the previous version of the draft. Here is the lyx version. The PDF version is at http://people.redhat.com/pbonzini/virtio-spec.pdf and the text version of the spec (interdiff from v1) is in a reply to this message. --- virtio-spec.lyx.saved 2011-11-29 14:00:59.782659120 +0100 +++ virtio-spec.lyx 2011-12-05 14:02:41.946266491 +0100 @@ -56,6 +56,7 @@ \html_math_output 0 \html_css_as_file 0 \html_be_strict false +\author 1531152142 "pbonzini" \end_header...

...s must therefore be prepared to handle both types of replies). I'm still not sure whether patch 6 is desirable; it didn't get any feedback in my v2 posting. In relation to v2, the subject line for patch 2 changed (the 'git backport-diff' tool doesn't handle that well), and the interdiff changes look bigger than they really are due to reflowed paragraphs. [----] : patches are identical [####] : number of functional differences between upstream/downstream patch [down] : patch is downstream-only The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively 001/6:[...