Jeff King <peff@xxxxxxxx> writes: > But the consequences, as you mention, could include data loss, which > argues for being on the safe side. In that case, we would probably want > an "xsetenv" to die() if we fail to avoid cluttering the code > everywhere. > > I dunno. If we're going to do it, it is probably maint-worthy. Junio? My gut feeling is xsetenv/xputenv would be sufficient. I do not think we make any setenv/putenv that we do not care about failing, perhaps other than the "if LESS is not there set it to this default value, as it would give users nicer experience if they use 'less'." -- 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