Re: bug: git name-rev --stdin --no-undefined on detached head
- From
- Erik Cervin Edin <erik@cervined.in>
- Date
- Dec 24, 2021, 11:44 UTC
- Message-ID
- <CA+JQ7M9xEHezQG0ui+jrhdWRHAausqxe5W7ucj4XkiLwnFL+Yw@mail.gmail.com>
- In-Reply-To
- <D22DF4C4-C98C-45FB-8D26-57B50A44FA3F@gmail.com>
> On Fri, Dec 24, 2021 at 7:09 AM John Cai <johncai86@gmail.com> wrote: > This would have the potential of breaking scripts that rely on the current behavior.
Presumably, using --no-undefined scripts rely on presumed behavior that doesn't exist. Similarly, using --name-only should expect to return a symbolic name While it's possible, I think it's rare that this would break scripts in an unacceptable way.
> On Fri, Dec 24, 2021 at 7:09 AM John Cai <johncai86@gmail.com> wrote: > Since I’m a bit new, I’m wondering how we generally handle these cases?
I'm also new so I can't really comment on this :) Though I believe the git suite in general is quite adamant on backwards compatibility