Re: [PATCH] I don't known anyone who understands what it means when they do a merge and see "file.txt: needs update". "file.txt: has changes" is much clearer.

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

 



Yeah: I was thinking about it earlier and came at the same conclusion.

There's a "porcelain" interface for a lot of commands. Does the concept need to be furthered for this case?

On another note - I've been running with this change for several days, and everything seems to be alright.

Tim



On May 5, 2008, at 10:35 AM, Avery Pennarun wrote:

On 5/3/08, Junio C Hamano <gitster@xxxxxxxxx> wrote:
"Avery Pennarun" <apenwarr@xxxxxxxxx> writes:
On 5/3/08, Junio C Hamano <gitster@xxxxxxxxx> wrote:
Of course not. Where does end-user scripts come into play when you are
running the testsuite?

I thought user scripts weren't supposed to rely on the porcelain
output?  It seems to change rather frequently anyway.

Wasn't the patch about changing output from "update-index --refresh",
which is as low as you can get?

Hmm, perhaps the problem then is that we're using plumbing output and
presenting it to the user as part of the porcelain.  Is there an
elegant way to fix that?

Avery

--
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]

  Powered by Linux