Re: [PATCH/RFC] improve no-op push output

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Junio C Hamano <gitster@xxxxxxxxx> writes:

>> would just print:
>>
>>   Everything up-to-date
>>
>> and now you get:
>>
>>   To /tmp/push-message/parent
>>    = [up to date]      master -> master
> [...]
>
> 	Everything up-to-date (the current branch not pushed)

I like both. They don't really take more screen space (1 more line for
Jeff, which is acceptable IMHO), and do add information.

I'd add the number of branches pushed in case it's not one, so it could
say one of:

  To /tmp/push-message/parent
   = [up to date]      master -> master

or

  Everything up-to-date (X branches pushed, including the current)

or

  Everything up-to-date (X branches pushed, not including the current)

It would give a clue to a user having created many local branches that
his local branches were not pushed, and vice-versa, may help people who
did not understand that "push.default=matching" was pushing multiple
branches.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]