On 11/05/2015 11:56 AM, Félix Sipma wrote:
> Hi!
>
> I just came to a solution which seems good for "mr -m update" (at least
> for my use case). It might interest someone else :-).
>
> [DEFAULT]
> git_update =
> git fetch origin
> git log HEAD..origin/master --oneline
I could see that bein
On 06/29/2015 05:11 PM, Joey Hess wrote:
> Seems to me that mr -m status is what you seek.
Nice - for the "status" command, that gives quiet results.
Operations like "mr -m update" are still inherently noisy, since
"git pull" isn't itself quiet when there's nothing to do. In
this case, git genera
Seems to me that mr -m status is what you seek.
--
see shy jo
___
vcs-home mailing list
vcs-home@lists.madduck.net
http://lists.madduck.net/listinfo/vcs-home
On 06/28/2015 11:03 AM, Adam Spiers wrote:
> Thanks for sharing!
>
> This reminds me of this very old thread
>
> http://lists.madduck.net/pipermail/vcs-home/2012-February/000705.html
>
> which unfortunately went nowhere due to Joey having concerns about
> "layering violations".
Wow - I guess t
Thanks for sharing!
This reminds me of this very old thread
http://lists.madduck.net/pipermail/vcs-home/2012-February/000705.html
which unfortunately went nowhere due to Joey having concerns about
"layering violations".
On 28 June 2015 at 14:34, Michael Henry wrote:
> On 06/25/2015 01:49 P
On 06/25/2015 01:49 PM, John Whitley wrote:
> Nice idea, Michael. It’s possible to prepend text only if
> some command has output.
I've never seen that particular trick with ``sed``, but I like
it. It's very compact and uses a standard tool instead of
hundreds of lines of Python, which makes it
Nice idea, Michael. It’s possible to prepend text only if some command has
output. E.g.:
git-status-prepend: https://gist.github.com/2264a228ea64e4313d11
#!/bin/sh
git -c color.status=always status -s | sed "1s/^/$*\\
/"
This would be used as:
git-status-prepend “mr status: /path/t
