Displaying 5 results from an estimated 5 matches for "reporting_bug".
Did you mean:
  reporting_bugs
  
2019 Jul 11
0
[p2v PATCH 4/4] podwrapper: adapt footer to p2v
---
 podwrapper.pl.in | 12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/podwrapper.pl.in b/podwrapper.pl.in
index f8b90ad..31fbb38 100755
--- a/podwrapper.pl.in
+++ b/podwrapper.pl.in
@@ -405,7 +405,8 @@ distributed for any purpose without any restrictions.
 my $reporting_bugs =
 "=head1 BUGS
 
-To get a list of bugs against libguestfs, use this link:
+To get a list of bugs against libguestfs (which include virt-p2v),
+use this link:
 L<https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools>
 
 To report a new bug agains...
2016 Jan 04
3
[PATCH 0/3] podwrapper: Generate consistent WARNING sections (RHBZ#1293527).
Fix for:
https://bugzilla.redhat.com/show_bug.cgi?id=1293527
Note that patches 2/3 and 3/3 are dependent on each other, ie.
applying 2/3 on its own will break the build.  So I may combine these
when applying the series.
Rich.
2019 Jul 11
5
[p2v PATCH 0/4] More imports and fixes
See individual patches for details.
Pino Toscano (4):
  Add valgrind suppression file
  podwrapper: the tools here start with p2v
  Import some internal documentation
  podwrapper: adapt footer to p2v
 .gitignore                 |   6 +
 Makefile.am                |   4 +-
 configure.ac               |   1 +
 docs/Makefile.am           |  65 ++++++++
 docs/p2v-building.pod      | 259
2019 Jul 09
7
[PATCH 0/5] Split virt-p2v in own repository
Hi,
as it was already discussed on this list, here it is my attempt in
splitting virt-p2v in an own repository.  Sadly there are things that
must be copied from libguestfs, as it cannot be avoided.
The approach taken was to run a script (will send separately) to just
get the "p2v" subdirectory with its history as own repository, and then
add in few followup commits all the bits needed
2009 May 03
6
[RFC] The reflink(2) system call.
Hi everyone,
	I described the reflink operation at the Linux Storage &
Filesystems Workshop last month.  Originally implemented as an
ocfs2-specific ioctl, the consensus was that it should be a syscall from
the get-go.  Here's some first-cut patches.
	For people who have not seen reflink, either at LSF or on the
ocfs2 wiki, the first patch contains
Documentation/filesystems/reflink.txt to