"W. Trevor King" writes:
> On Wed, Jul 16, 2014 at 07:36:10PM -0300, David Bremner wrote:
>> W. Trevor King writes:
>> > If we don't have an upstream, there is nothing to merge, so
>> > nothing is unmerged. This avoids errors like:
>>
>> pushed this one patch.
>
> Without the stderr-catching
W. Trevor King wk...@tremily.us writes:
On Wed, Jul 16, 2014 at 07:36:10PM -0300, David Bremner wrote:
W. Trevor King writes:
If we don't have an upstream, there is nothing to merge, so
nothing is unmerged. This avoids errors like:
pushed this one patch.
Without the stderr-catching of
"W. Trevor King" writes:
> On Wed, Jul 16, 2014 at 07:36:10PM -0300, David Bremner wrote:
>> W. Trevor King writes:
>> > If we don't have an upstream, there is nothing to merge, so
>> > nothing is unmerged. This avoids errors like:
>>
>> pushed this one patch.
>
> Without the stderr-catching
W. Trevor King wk...@tremily.us writes:
On Wed, Jul 16, 2014 at 07:36:10PM -0300, David Bremner wrote:
W. Trevor King writes:
If we don't have an upstream, there is nothing to merge, so
nothing is unmerged. This avoids errors like:
pushed this one patch.
Without the stderr-catching of
On Thu, Jul 17, 2014 at 06:28:55AM -0300, David Bremner wrote:
W. Trevor King writes:
On Wed, Jul 16, 2014 at 07:36:10PM -0300, David Bremner wrote:
W. Trevor King writes:
If we don't have an upstream, there is nothing to merge, so
nothing is unmerged. This avoids errors like:
W. Trevor King wk...@tremily.us writes:
If we don't have an upstream, there is nothing to merge, so nothing is
unmerged. This avoids errors like:
pushed this one patch.
d
___
notmuch mailing list
notmuch@notmuchmail.org
On Wed, Jul 16, 2014 at 07:36:10PM -0300, David Bremner wrote:
W. Trevor King writes:
If we don't have an upstream, there is nothing to merge, so
nothing is unmerged. This avoids errors like:
pushed this one patch.
Without the stderr-catching of something like patch 3, this means
folks
"W. Trevor King" writes:
> - my $fetch_head = git ('rev-parse', $commit);
> + my ($fetch_head, $status) = git_with_status ('rev-parse', $commit);
> + if ($status) {
> +return 0;
> + }
Could there be other errors here, other than @{upstream} not existing?
At first glance it seems like
On Tue, Jul 15, 2014 at 08:44:53PM -0300, David Bremner wrote:
> W. Trevor King writes:
> > - my $fetch_head = git ('rev-parse', $commit);
> > + my ($fetch_head, $status) = git_with_status ('rev-parse', $commit);
> > + if ($status) {
> > +return 0;
> > + }
>
> Could there be other errors
W. Trevor King wk...@tremily.us writes:
- my $fetch_head = git ('rev-parse', $commit);
+ my ($fetch_head, $status) = git_with_status ('rev-parse', $commit);
+ if ($status) {
+return 0;
+ }
Could there be other errors here, other than @{upstream} not existing?
At first glance it
On Tue, Jul 15, 2014 at 08:44:53PM -0300, David Bremner wrote:
W. Trevor King writes:
- my $fetch_head = git ('rev-parse', $commit);
+ my ($fetch_head, $status) = git_with_status ('rev-parse', $commit);
+ if ($status) {
+return 0;
+ }
Could there be other errors here, other
If we don't have an upstream, there is nothing to merge, so nothing is
unmerged. This avoids errors like:
$ nmbug status
error: No upstream configured for branch 'master'
error: No upstream configured for branch 'master'
fatal: ambiguous argument '@{upstream}': unknown revision or path
12 matches
Mail list logo
