quilt-dev
[Top][All Lists]
Advanced

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

Re: [Quilt-dev] Proposed update to the fork help


From: Andreas Gruenbacher
Subject: Re: [Quilt-dev] Proposed update to the fork help
Date: Wed, 20 Apr 2005 00:04:53 +0200
User-agent: KMail/1.7.1

On Tuesday 19 April 2005 23:41, Jean Delvare wrote:
> Hi all,
>
> As discussed in an earlier thread, I think that the "fork" command of
> quilt isn't properly documented. There is an explanation of what it is
> meant for in the quilt introduction document (PDF), but nothing in
> "quilt fork -h", where users would look for it IMHO.
>
> What about the following?
>
>   Fork the topmost patch.  Forking a patch means creating a verbatim
>   copy of it under a new name, and use that new name instead of the
>   original one in the current series.  This is useful when a patch
>   has to be modified, but the original version of it needs to be
        I changed "needs to" to "should".
>   preserved, e.g. because it is used in another series, or for the
>   history.  A typical sequence of commands would be: fork, edit,
>   refresh.
>
>   If new_name is missing, the name of the forked patch will be the
>   current patch name, followed by "-2".  If the patch name already
>   ends in a dash-and-number, the number is further incremented
>   (e.g., patch.diff, patch-2.diff, patch-3.diff).

The change is in.

> Thanks to Greg KH for his early review of this proposed text update.

;)

Thanks,
-- 
Andreas Gruenbacher <address@hidden>
SUSE Labs, SUSE LINUX PRODUCTS GMBH




reply via email to

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