From: David Bremner <bremner@debian.org>
To: "W. Trevor King" <wking@tremily.us>, notmuch@notmuchmail.org
Cc: Tomi Ollila <tomi.ollila@iki.fi>
Subject: Re: [PATCH 1/4] nmbug: Add a git_with_status helper function
Date: Wed, 16 Jul 2014 06:36:22 -0300 [thread overview]
Message-ID: <87a989abmx.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <6ed6edd459cd50402d7e4abc50a6967709e08f16.1404678709.git.wking@tremily.us>
"W. Trevor King" <wking@tremily.us> writes:
> Sometimes we want to catch Git errors and handle them, instead of
> dying with an error message. This lower-level version of git() allows
> us to get the error status when we want it.
pushed this one patch.
d
next prev parent reply other threads:[~2014-07-16 9:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-06 20:40 [PATCH 0/4] nmbug without an upstream repository (and init) W. Trevor King
2014-07-06 20:40 ` [PATCH 1/4] nmbug: Add a git_with_status helper function W. Trevor King
2014-07-16 9:36 ` David Bremner [this message]
2014-07-06 20:40 ` [PATCH 2/4] nmbug: Handle missing @upstream in is_unmerged W. Trevor King
2014-07-15 23:44 ` David Bremner
2014-07-16 0:11 ` W. Trevor King
2014-07-16 22:36 ` David Bremner
2014-07-16 23:03 ` W. Trevor King
2014-07-17 9:28 ` David Bremner
2014-07-17 18:38 ` W. Trevor King
2014-07-19 12:34 ` David Bremner
2014-07-06 20:40 ` [PATCH 3/4] nmbug: Catch stderr " W. Trevor King
2014-07-15 23:49 ` David Bremner
2014-07-16 0:17 ` W. Trevor King
2014-07-16 10:04 ` David Bremner
2014-07-06 20:40 ` [PATCH 4/4] nmbug: Add an 'init' command W. Trevor King
2014-07-15 23:54 ` David Bremner
2014-07-16 0:12 ` W. Trevor King
2014-09-15 16:13 ` David Edmondson
2014-09-15 16:25 ` W. Trevor King
2014-09-15 16:32 ` David Edmondson
2014-09-15 16:35 ` W. Trevor King
2014-09-15 18:09 ` David Bremner
2014-09-15 18:13 ` W. Trevor King
2014-09-23 18:44 ` [PATCH] potential fix for nmbug merge problems David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a989abmx.fsf@maritornes.cs.unb.ca \
--to=bremner@debian.org \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
--cc=wking@tremily.us \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).