From: Ivy Foster
They're all generated during make.
---
I was going to add BUILDINFO.5 to the list, but this way covers future
additions.
doc/.gitignore | 14 +-
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git a/doc/.gitignore b/doc/.gitignore
index
On 02/10/18 at 10:15pm, i...@escondida.tk wrote:
> From: Ivy Foster
>
> Since using atexit(3) draws in stdlib anyway and this changes every
> exit call at large and return call in main(), go ahead and use
> EXIT_SUCCESS and EXIt_FAILURE, too.
>
> Signed-off-by: Ivy Foster
On 02/10/18 at 10:15pm, i...@escondida.tk wrote:
> From: Ivy Foster
>
> Signed-off-by: Ivy Foster
> ---
There are two major changes here: adding short options to the usage
and the "simplification" of the usage function. The short options
should be added
From: Ivy Foster
Previously, it also parsed the config file instead of simply setting
the (global) config_file variable
Signed-off-by: Ivy Foster
---
src/pacman/pacman-conf.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git
From: Ivy Foster
Signed-off-by: Ivy Foster
---
src/pacman/pacman-conf.c | 40
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/src/pacman/pacman-conf.c b/src/pacman/pacman-conf.c
index
From: Ivy Foster
Since using atexit(3) draws in stdlib anyway and this changes every
exit call at large and return call in main(), go ahead and use
EXIT_SUCCESS and EXIt_FAILURE, too.
Signed-off-by: Ivy Foster
---
src/pacman/pacman-conf.c | 29
From: Ivy Foster
This allows MYNAME to be used in place of the literal string
"pacman-conf" in usage
Signed-off-by: Ivy Foster
---
src/pacman/pacman-conf.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git
From: Ivy Foster
Signed-off-by: Ivy Foster
---
This verion of the patch simply drops the check for '?', since it's
caught by "default" anyway. The other patches are unchanged, except
where rebased against this modified patch.
src/pacman/pacman-conf.c | 3
From: Ivy Foster
Signed-off-by: Ivy Foster
---
As per agregory's request in #archlinux-pacman, this version of the
patch leaves the check for '?' well enough alone. '?' is
getopt_long(3)'s way of indicating user error, and we can think of
default: as
From: Ivy Foster
Previously, it also parsed the config file instead of simply setting
the (global) config_file variable
Signed-off-by: Ivy Foster
---
src/pacman/pacman-conf.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git
From: Ivy Foster
This allows MYNAME to be used in place of the literal string
"pacman-conf" in usage
Signed-off-by: Ivy Foster
---
src/pacman/pacman-conf.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git
From: Ivy Foster
Signed-off-by: Ivy Foster
---
src/pacman/pacman-conf.c | 40
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/src/pacman/pacman-conf.c b/src/pacman/pacman-conf.c
index
On 02/10/18 at 10:15pm, i...@escondida.tk wrote:
> From: Ivy Foster
>
> Previously, it also parsed the config file instead of simply setting
> the (global) config_file variable
I think the original purpose of this patch is fundamentally
unnecessary, but it does (accidentally,
From: Yen Chi Hsuan
Before this change, LC_TIME=zh_TW.UTF-8 makepkg has the following line:
==> Making package: foobar 1-1 (日 2月 11 01:13:42 CST 2018)
With this patch, this line becomes:
==> Making package: foobar 1-1 (西元2018年02月11日 (週日) 01時13分57秒)
The latter is more
14 matches
Mail list logo