From: Kevin D <me@ikke.info>
To: epilys <epilys@norn.io>
Cc: git@vger.kernel.org, gitster@pobox.com, peff@peff.net
Subject: Re: [PATCH] forbid log --graph --no-walk
Date: Sat, 14 Mar 2015 23:42:42 +0100 [thread overview]
Message-ID: <20150314224242.GA3311@vps892.directvps.nl> (raw)
In-Reply-To: <5504A8CF.9080202@norn.io>
Subject is usually prefixed with the part that is changed, in this case
log.
For example:
log: forbid log --graph --no-walk
On Sat, Mar 14, 2015 at 11:31:59PM +0200, epilys wrote:
> In git-log, --graph shows a graphical representation of a
> continuous commit history, and --no-walk shows discrete specified
> commits without continuity. This doesn't make sense, so we forbid the
> combined use of these flags.
>
> Signed-off-by: Manos Pitsidianakis <epilys@norn.io>
> ---
> builtin/log.c | 2 ++
> t/t4202-log.sh | 4 ++++
> 2 files changed, 6 insertions(+)
>
> diff --git a/builtin/log.c b/builtin/log.c
> index dd8f3fc..0194133 100644
> --- a/builtin/log.c
> +++ b/builtin/log.c
> @@ -155,6 +155,8 @@ static void cmd_log_init_finish(int argc, const char
> **argv, const char *prefix,
> memset(&w, 0, sizeof(w));
> userformat_find_requirements(NULL, &w);
> + if (rev->graph && rev->no_walk)
Patch got corrupted here (Space before +)
> + die("--graph and --no-walk are incompatible");
> if (!rev->show_notes_given && (!rev->pretty_given || w.notes))
> rev->show_notes = 1;
> if (rev->show_notes)
> diff --git a/t/t4202-log.sh b/t/t4202-log.sh
> index 5f2b290..4dd939b 100755
> --- a/t/t4202-log.sh
> +++ b/t/t4202-log.sh
> @@ -887,4 +887,8 @@ test_expect_success GPG 'log --graph
> --show-signature for merged tag' '
> grep "^| | gpg: Good signature" actual
> '
> +test_expect_success 'forbid log --graph --no-walk' '
Here also
> + test_must_fail git log --graph --no-walk
> +'
> +
> test_done
next prev parent reply other threads:[~2015-03-14 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 21:31 [PATCH] forbid log --graph --no-walk epilys
2015-03-14 22:42 ` Kevin D [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-14 21:35 epilys
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=20150314224242.GA3311@vps892.directvps.nl \
--to=me@ikke.info \
--cc=epilys@norn.io \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).