git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Faye-Lund <kusmabite@gmail.com>
To: git@vger.kernel.org
Cc: normalperson@yhbt.net
Subject: [PATCH] git-svn: forward -q to git-rebase
Date: Tue, 12 Jun 2012 17:43:35 +0200	[thread overview]
Message-ID: <1339515815-10752-1-git-send-email-kusmabite@gmail.com> (raw)

When calling "git svn rebase -q", we still get the message
"Current branch BRANCHNAME is up to date." from git-rebase, which
isn't quite as quiet as we could be.

Fix this by forwarding the -q flag to git-rebase.

Signed-off-by: Erik Faye-Lund <kusmabite@gmail.com>
---

I just set up a cronjob that did a "git svn rebase -q", and noticed
it triggered cron to send me an e-mail every time.

Since I'm not really interested in getting an e-mail every time the
script does nothing, but I'd like the option to get an e-mail whenever
it does something useful, perhaps something like this can benefit
other people as well?

 git-svn.perl | 1 +
 1 file changed, 1 insertion(+)

diff --git a/git-svn.perl b/git-svn.perl
index 0b074c4..34baa43 100755
--- a/git-svn.perl
+++ b/git-svn.perl
@@ -1590,6 +1590,7 @@ sub cmd_gc {
 sub rebase_cmd {
 	my @cmd = qw/rebase/;
 	push @cmd, '-v' if $_verbose;
+	push @cmd, '-q' if $_q;
 	push @cmd, qw/--merge/ if $_merge;
 	push @cmd, "--strategy=$_strategy" if $_strategy;
 	push @cmd, "--preserve-merges" if $_preserve_merges;
-- 
1.7.11.rc2.5.g68f532f.dirty

             reply	other threads:[~2012-06-12 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 15:43 Erik Faye-Lund [this message]
2012-06-12 16:54 ` [PATCH] git-svn: forward -q to git-rebase Junio C Hamano
2012-06-12 20:23   ` Erik Faye-Lund
2012-06-12 20:39     ` Erik Faye-Lund
2012-06-12 20:41       ` Erik Faye-Lund
2012-06-12 21:38 ` Eric Wong

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=1339515815-10752-1-git-send-email-kusmabite@gmail.com \
    --to=kusmabite@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=normalperson@yhbt.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).