From: Erik Faye-Lund <kusmabite@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, normalperson@yhbt.net
Subject: Re: [PATCH] git-svn: forward -q to git-rebase
Date: Tue, 12 Jun 2012 22:23:46 +0200 [thread overview]
Message-ID: <CABPQNSYxq1cSYKi+fGajoASL6x7e6VCaSDoWNmYuEHSgt8NFBA@mail.gmail.com> (raw)
In-Reply-To: <7vd354jwss.fsf@alter.siamese.dyndns.org>
On Tue, Jun 12, 2012 at 6:54 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Erik Faye-Lund <kusmabite@gmail.com> writes:
>
>> 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?
>
> If it matches what you would get from "git pull -q" run in a
> cronjob, I would say that is a sensible change to make.
Seems like it to me in my tests, yeah.
next prev parent reply other threads:[~2012-06-12 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 15:43 [PATCH] git-svn: forward -q to git-rebase Erik Faye-Lund
2012-06-12 16:54 ` Junio C Hamano
2012-06-12 20:23 ` Erik Faye-Lund [this message]
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=CABPQNSYxq1cSYKi+fGajoASL6x7e6VCaSDoWNmYuEHSgt8NFBA@mail.gmail.com \
--to=kusmabite@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).