| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is an attempt to create a better tar-wrapper that can be run in
%prep context in a scratch directory, and create a copy of the extracted
files in QUILT_WORKDIR.
Try out as follows:
$ cd experiment
$ export QUILT_WORKDIR=work
$ mkdir work
$ PATH=.:$PATH
$ wget https://cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.7.4.tar.xz
$ tar -xaf linux-6.7.4.tar.xz # this creates linux-6.7.4/ and work/linux-6.7.4/
$ tar -xaf linux-6.7.4.tar.xz # when run again:
Refusing to overwrite linux-6.7.4
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The paragraph explaining the limitations on spec files wasn't clear
to all, so reword one statement and add an example to make it
hopefully clearer.
Signed-off-by: Jean Delvare <jdelvare@suse.de>
|
|
|
|
|
| |
Signed-off-by: Jean Delvare <jdelvare@suse.de>
Fixes: b969b6ee1edc ("Update the Japanese translation")
|
|
|
|
|
|
|
| |
Files can be removed in any order, it isn't deterministic, so loosen
the test to accept any order.
Signed-off-by: Jean Delvare <jdelvare@suse.de>
|
|
|
|
|
|
|
|
| |
Gawk version 5.0.0 and later will complain when escaping a sequence
in a regexp, which didn't need to be escaped. Drop the unneeded
escape character to silent the warning.
Signed-off-by: Jean Delvare <jdelvare@suse.de>
|
|
|
|
| |
Signed-off-by: Yasushi SHOJI <yashi@spacecubics.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Add support for zstd compressed archives (*.tar.zst) and patches.
[JD: Change the file output match pattern to "Zstandard compressed
data" to prevent false positives.]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The install-sh script we ship has issues. It is not able to install
multiple files at once, and is unable to create directories when all
their parent elements do not already exist.
Update to a more recent version of that script where these issues are
fixed. Also set the executable bit so that the script can actually be
run.
This fixes bug #64430:
https://savannah.nongnu.org/bugs/index.php?64430
Signed-off-by: Jean Delvare <jdelvare@suse.de>
|
|
|
|
|
|
|
|
|
|
| |
Fix the file name heuristic to also find quoted file names in
unapplied patches.
This fixes bug #41708:
https://savannah.nongnu.org/bugs/index.php?41708
Signed-off-by: Jean Delvare <jdelvare@suse.de>
|
|
|
|
|
|
|
|
|
| |
GNU diff quotes file names which contain a space, and GNU patch
expects that as well (oddly enough, only when the patch header does
not include timestamps). Do the same so that the patches we generate
can always be applied.
Signed-off-by: Jean Delvare <jdelvare@suse.de>
|
|
|
|
|
|
|
| |
If a patch can't be removed cleanly, suggest running "quilt diff -z"
to spot the pending changes.
Signed-off-by: Jean Delvare <jdelvare@suse.de>
|
|
|
|
|
|
|
|
| |
Just like commit 4dfe7f9, (test: Fix a race condition, 2023-01-20),
this fix a test race when stdout and stderr in any order.
Signed-off-by: Đoàn Trần Công Danh <congdanhqx@gmail.com>
Signed-off-by: Jean Delvare <jdelvare@suse.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test suite does not differentiate between stdout and stderr. When
messages are printed to both, the order in which they will reach us
is apparently not guaranteed. Ideally this would be deterministic, but
until then, explicitly test stdout and stderr separately in the test
case itself. Otherwise the test suite fails randomly, which is a pain
for distribution package maintainers.
This fixes bug #63651 reported by Ross Burton:
https://savannah.nongnu.org/bugs/index.php?63651
Signed-off-by: Jean Delvare <jdelvare@suse.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The ln defaults can be slightly different depending on the platform.
While on Linux 'ln' defaults to 'ln -P', on Solaris (and possibly
other platforms) it defaults to 'ln -L'.
This difference is best resolved by explicitly using the '-P' flag.
This fixes bug #63451:
https://savannah.nongnu.org/bugs/index.php?63451
Credits to the anonymous reporter.
[JD: Propagate the fix to all occurrences of 'ln'.]
Signed-off-by: Jean Delvare <jdelvare@suse.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Quilt setup can't be used on arbitrary spec files. Due to the fact
that quilt only deals with patches, every other modification to the
working tree has to happen first, and the patches must be applied
last.
This is a design limitation and not a bug, but document it so that
the users are aware of it and can adjust the %prep section of their
spec file if needed.
Signed-off-by: Jean Delvare <jdelvare@suse.de>
|
|
|
|
|
|
|
| |
Now that quote_bre() has been split into quote_re_grep() and
quote_re_sed(), rename quote_re() to quote_awk_re() for consistency.
Signed-off-by: Jean Delvare <jdelvare@suse.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GNU grep version 3.8 became more strict about needless quoting in
patterns. We have one occurrence of that in quilt, where "/"
characters are being quoted by default. There are cases where they
indeed need to be quoted (typically when used in a sed s/// command)
but most of the time they do not, and this results in the following
warning:
grep: warning: stray \ before /
So rename quote_bre() to quote_sed_re(), and introduce
quote_grep_re() which does not quote "/".
Signed-off-by: Jean Delvare <jdelvare@suse.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These are ANSI escape sequences as defined by ECMA-48; recast the entire
discussion in light of that fact.
Condense the many tagged paragraphs with a templated discussion of
defaults into a table.
Sort the QUILT_COLORS format names into alphabetical order.
Add a hint to the formatter (man) to call the tbl preprocessor to
render the table.
Expand the example to be more demonstrative.
Add pointers to the ECMA-48 standard document and the console_codes
section 4 man page (from Michael Kerrisk's man-pages project, widely
available) to the See Also section.
[JD: Some fixes, added patch_offs to the table, added a note that the
patches command shares colors with the series command]
|
|
|
|
|
|
|
| |
Use the groff extension .schar to provide an alternative output sequence
for output devices missing the Unicode box-drawing characters.
[JD: removed a .fi request which I believed was restored by accident]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Give working tree example a name that looks more like an actual
software project's directory name.
* Fix pronoun/antecedent agreement (multiple occurrences).
* Tighten language (e.g., unnecessary use of "some").
* Reorganize discussion of how quilt finds its rc file to proceed
strictly in the order attempted.
* Leave breadcrumbs about EDITOR and LESS, which used to be part of this
discussion; add cross-reference to where the material is now.
* Make explicit the fact that quilt command names need to be manually
up-cased for use in QUILT_COMMAND_ARGS.
* Set configuration variable names in italics.
* Transform a popular Denglish construction into idiomatic English.
https://english.stackexchange.com/questions/85069/is-the-construction-it-allows-to-proper-english
* Clarify that "if set to anything" variables function as Booleans.
* Recast "a shortcut to" as "shorthand for", which is more idiomatic
English in context.
* Add cross-reference to diffstat man page on first occurrence.
* Fix typo: each commands -> each command.
[JD: reverted 2 changes I did not like; fixes one more typo]
|
|
|
|
|
|
| |
* Remove dependent clause used as a topic transition when this material
was not in its own section.
* Provide examples of when $EDITOR is used.
|
|
|
|
| |
* Eliminate otherwise unused term "sub-command".
|
|
|
|
|
|
|
|
| |
* Don't introduce a metavariable without explaining it or using it in
context.
* Drop the reference to the PDF documentation which doesn't belong
there.
* Clarify options --trace and --version.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Don't end a sentence with an abbreviation period if possible (also,
man-pages(7) discourages the use of Latin abbreviations altogether).
* Users of quilt are not merely outputting patches; they are consuming
them and altering them as well.
* Clarify the (shall we say) truncability of command names.
* Use directional double-quotes instead of boldface to set off literals.
Some typographers claim that frequent font face changes tire the eye.
* Offer an example of a patch name.
* Introduce the "quilt series" command in the same paragraph the series
file itself is first described, to eliminate forward reference.
* Introduce quilt command names only once each.
* Add a paragraph summarizing the work cycle for starting and refining a
new patch.
[JD: Some editions and clean-ups]
|
| |
|
|
|
|
| |
Per style recommendation in man-pages(7).
|
|
|
|
| |
Everything in manual sections 1 or 8 is a tool, in some sense.
|
| |
|
| |
|
|
|
|
| |
Also add a clarifying introductory sentence.
|
|
|
|
|
|
|
|
| |
Variable content in an italic context is set in roman for contrast, but
still in italics in running roman prose.
[JD: Revert some of the changes which did not belong there, and
restored the original indentation level as I think it looked better]
|
|
|
|
|
|
|
|
|
|
|
| |
Embolden internal subsection reference, and refer to its parent section.
Point explicitly to the GNU Diffutils manual regarding unified diff
format, and add cross-reference in the See Also section.
Add cross-reference to diffstat man page.
Sort man page cross-reference list in alphabetical order.
|
|
|
|
| |
...including names of software projects (such as quilt itself).
|
|
|
|
|
|
|
|
| |
The Latin "exempli gratia" is abbreviated "e.g.".
Also, use a zero-width-space escape to defeat roff's end-of-sentence
detection. See section 4.1 of CSTR #54, "Troff User's Manual", Ossanna
& Kernighan <https://www.troff.org/54.pdf>.
|
|
|
|
| |
Also add quotation marks where they make semantic sense.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Document --quiltrc, --trace, and --version options explicitly.
Separate the informational operation modes for reporting help and
version information.
Mark up synopsis canonically (literals in bold, variable content in
italics, and roman for "synopsis language" (option brackets, etc.)).
Use groff_man(7)'s SY and YS macros for more attractive presentation.
[JD: Restore [options] and strip duplicate line]
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a "literal" ASCII 45 hyphen-minus character is desired, it has to
be escaped; this is a requirement going all the way back to Bell Labs
Troff, but is frequently overlooked. Getting it right enables
accurate cut-and-paste of code examples, filenames, URLs, and so forth
from roff documents prepared for UTF-8 terminal and PDF output, possibly
among others.
See section 2.1 of CSTR #54, "Troff User's Manual", Ossanna & Kernighan
<https://www.troff.org/54.pdf>.
|
|
|
|
|
|
| |
This eliminates the use of low-level requests in this man page (the
groffism ".fam" to change the font family and the switching off and on
of fill mode with ".nf" and ".fi".)
|
|
|
|
|
| |
Apart from being higher-level and easier to read, the macros get you
proper italic corrections when abutting italic with non-italic text.
|
|
|
|
|
|
|
|
| |
Use only section names endorsed by man-pages(7), and put them in the
recommended order.
Use subsection macro (SS) where helpful.
[JD: Preserve the EXAMPLE section as EXAMPLES]
|
|
|
|
|
|
|
| |
Also reflow input lines to 72 columns.
Both are recommended by *roff experts:
https://www.gnu.org/software/groff/manual/html_node/Input-Conventions.html
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Blank lines are bad roff style. Per CSTR #54, blank lines are the
equivalent of ".sp 1", but in GNU roff this can be overridden with a
blank line macro (".blm"), and all macro packages for text formatting
(mm, ms, me, man, etc.) have macros for paragraph separation, and the
inter-paragraph spacing is usually different from ".sp 1" for typesetter
output (this can be seen in PostScript and PDF output). Explicit
spacing is also unnecessary immediately adjacent to section headings.
See section 5.3 of CSTR #54, "Troff User's Manual", Ossanna & Kernighan
<https://www.troff.org/54.pdf>.
[JD: Added an empty request (.) before each section to preserve the
readability of the input.]
|
|
|
|
|
|
|
|
|
|
| |
This causes warnings from roff when the warning level is turned up
really high, as some roff/man page hackers do.
<standard input>:891: warning: number register `an-saved-margin2' not defined
<standard input>:891: warning: number register `an-saved-prevailing-indent2' not defined
Stop supplying the extraneous argument.
|