Re: [PATCH] git-svn: forward -q to git-rebase
- From
Erik Faye-Lund <kusmabite@gmail.com>
- Date
- Jun 12, 2012, 20:39 UTC
- Message-ID
- <CABPQNSZN7zzF4rki38x3PHXT2DZhOjUtUVGNx2mY-wnQtCj-pA@mail.gmail.com>
- In-Reply-To
- <CABPQNSYxq1cSYKi+fGajoASL6x7e6VCaSDoWNmYuEHSgt8NFBA@mail.gmail.com>
On Tue, Jun 12, 2012 at 10:23 PM, Erik Faye-Lund <kusmabite@gmail.com> wrote:
Show 24 quoted lines
> 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.
Hm, but not the same as "git pull --rebase -q", as git-pull.sh doesn't forward $verbosity to "git rebase" either. It DOES pass it to "git merge", though... Which puzzles me a bit.