2013/5/20 Holger Hellmuth <holger@xxxxxxxxxx>: > Am 19.05.2013 18:56, schrieb Ralf Thielow: > >> 2013/5/16 Holger Hellmuth (IKS) <hellmuth@xxxxxxxxxx>: >>> >>> >> [...] >>>> >>>> + reset = neu setzen (maybe "umsetzen"?) >>> >>> >>> >>> "zurücksetzen" >>> >> >> "reset" can be used with every existing commit. "zurücksetzen" >> would imply that it have to be a recent commit, no? > > > It implies that it sets to something that already existed or came before. > So it even fits in a case where you reset to an older commit and reset back > to HEAD because the HEAD commit existed already. > > If you still don't like it, I would prefer "umsetzen" to "neu setzen". > I'd still understand "zurücksetzen" as "set something *back* to" but this "back" can also be something that was made after HEAD perhaps on another branch and HEAD (or the current ref) was never at this point before, so "zurücksetzen" is not true in this case. I prefer "umsetzen" to "neu setzen", too. I'll change the glossary to this. Thanks > -- > 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 -- 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