On Mon, Feb 08, 2016 at 12:25:58PM +0100, Sebastian Schuberth wrote: > On 2/5/2016 14:58, Jeff King wrote: > > >Yeah, I agree it's unlikely. And the output is already ambiguous, as the > >first field could be a blob (though I guess the caller knows if they > >passed "--blob" or not). If we really wanted an unambiguous output, we > >could have something like "file:...", "blob:...", etc. But that's a bit > >less readable for humans, and I don't think solves any real-world > >problems. > > > >So I think it would be OK to use "<command line>" here, as long as the > >token is documented. > > Thinking about it again, I actually do like Peff's prefix solution better. > It would solve the real-world problem that my proposed "<command line>" > marker could in fact be a file name.
I'm OK with that direction, but I think it will need some more infrastructure in the config code (right now we just set "name" to some string without recording its type). It probably would not be too hard to add, though. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
