From: ludo@gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org, Hartmut Goebel <h.goebel@goebel-consult.de>
Subject: Re: [PATCH] scripts: hash: Add --exclude-.git option.
Date: Tue, 06 Sep 2016 14:26:58 +0200 [thread overview]
Message-ID: <87wpiprz71.fsf@gnu.org> (raw)
In-Reply-To: <87bn01y1pk.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Tue, 06 Sep 2016 08:36:07 +0200")
Jan Nieuwenhuizen <janneke@gnu.org> skribis:
>> What about --exclude-vcs/-x? Tar uses that name, although with slightly
>> different semantics (info "(tar) exclude").
>
> Yes, I like this even better than my 2nd --exclude=FILE patch.
I prefer --exclude-vcs too because that’s the main use case, so it’s
best to have a shortcut.
> From 060f9123acd4c6771e976c5442361285f8c8bc89 Mon Sep 17 00:00:00 2001
> From: Jan Nieuwenhuizen <janneke@gnu.org>
> Date: Tue, 6 Sep 2016 08:28:33 +0200
> Subject: [PATCH] scripts: hash: Add --exclude-vcs option.
>
> * guix/scripts/hash.scm (show-help): Add help text for --exclude-vcs option.
> (%options): Add --exclude-vcs option.
> (guix-hash): Handle exclude-vcs option.
> * doc/guix.texi ("Invoking guix hash"): Update doc.
> * tests/guix-hash.sh: Add test.
OK for me! If there are no objections, I’ll commit this one.
Ludo’.
next prev parent reply other threads:[~2016-09-06 12:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 8:43 [PATCH] scripts: hash: Add --exclude-.git option Jan Nieuwenhuizen
2016-09-05 9:20 ` Hartmut Goebel
2016-09-05 10:56 ` Vincent Legoll
2016-09-05 11:36 ` Jan Nieuwenhuizen
2016-09-05 20:20 ` Efraim Flashner
2016-09-05 21:04 ` Jan Nieuwenhuizen
2016-09-05 21:14 ` Leo Famulari
2016-09-05 20:50 ` Leo Famulari
2016-09-05 20:49 ` Danny Milosavljevic
2016-09-05 20:52 ` Leo Famulari
2016-09-05 21:33 ` Ludovic Courtès
2016-09-06 6:36 ` Jan Nieuwenhuizen
2016-09-06 12:26 ` Ludovic Courtès [this message]
2016-09-07 10:02 ` Ludovic Courtès
2016-09-06 6:48 ` Vincent Legoll
2016-09-06 12:24 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpiprz71.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=h.goebel@goebel-consult.de \
--cc=janneke@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.