Re: Newbie grief

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


Carlos Martín Nieto <cmn@xxxxxxxx> writes:

> On Thu, 2012-05-03 at 22:25 -0700, Junio C Hamano wrote:
>> Michael Witten <mfwitten@xxxxxxxxx> writes:
>> 
>> > As for a seemingly conservative suggestion, how about using a little
>> > more structural white space:
>> >
>> >   To $uri_for_central_repo
>> >    ! [rejected]        HEAD -> feature_0 (non-fast-forward)
>> >
>> >   error: failed to push some refs to '$uri_for_central_repo'
>> >
>> >   To prevent you from losing history, non-fast-forward updates were rejected
>> >   Merge the remote changes (e.g. 'git pull') before pushing again.  See the
>> >   'Note about fast-forwards' section of 'git push --help' for details.
>> >
>> > Alas! Error output like this is constructed in the code in a way that
>> > potentially makes adding such white space non-trivial.
>> >
>> > Perhaps the error message system needs an overhall; rather than spitting
>> > out error messages from anywhere, they ought to be corralled and collated
>> > by a dedicated subsystem.
>> 
>> Didn't somebody recently rework these messages quite extensively?
>
> If you're thinking of me,...

No, I was referring to f25950f (push: Provide situational hints for
non-fast-forward errors, 2012-03-20).
--
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


[Newbies FAQ]     [Linux Kernel Development]     [Free Online Dating]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Free Online Dating]     [Photo]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]     [Linux Resources]

Add to Google