[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-tar] Status of feature request: ignore requested members missing in

From: Vladimir A . Pavlov
Subject: [Bug-tar] Status of feature request: ignore requested members missing in archive
Date: Mon, 21 Jul 2014 22:33:14 +0400

Dear tar developers!

Could you please clarify the status of my previous email with a patch for
feature request: 
http://lists.gnu.org/archive/html/bug-tar/2014-06/msg00003.html ?

The only person replied to it was Pavel Raiskup but even he didn't give me
a definite answer. Suggested star unfortunatelly doesn't fulfil my needs as 

Is there a chance the patch will be accepted upstream? Are you busy currently
and have I just to wait more? Is the feature not useful enough to be implemented
in gnu tar? Do I have to write more docs or rewrite the patch in some way for 
to consider the patch? Did you just missed the email? Is the patch too ugly and
will never be accepted?

I'd really like to have the patch commited to tar but more than that I'd like to
understand whether I should expect positive answer or not. Should/can I do
anything for the patch to be applied?

P.S. I'm sorry that the previous email had a bug in examples. Below is the
     fixed version:

> It's sometimes useful to ignore errors tar returns if a requested member
> is not found in archive, while receiving other possible errors (corrupt or
> absent archives, no space left on device, etc).
> For example:
> $ touch file
> $ tar -c file | tar -t dir
> tar: dir: Not found in archive
> tar: Exiting with failure status due to previous errors
> $ echo $?
> 2
> $
> The attached patch implements a new option 
> --ignore-missing/--no-ignore-missing
> which allows the behavior wanted:
> $ touch file
> $ tar -c file | tar --ignore-missing -t dir
> $ echo $?
> 0
> $
> 1. Any chances it will (can) get to future official releases?
> 2. Are there modifications needed for the patch to be done to be accepted to 
> upstream?

Vladimir A. Pavlov

reply via email to

[Prev in Thread] Current Thread [Next in Thread]