Re: Possible bug report: git checkout tag problem
Hi Myles, On Mon, 8 Jan 2018, Myles Fong wrote: > Brief description: > When two tags are pointing to the same commit, e.g. tagA and tagB, if I > do `git checkout tagA` then `git checkout tagB`, and then `git status`, > it shows `HEAD detached at tagA` > > Expected behaviour: > I'm expecting it to show `HEAD detached at tagB`, though I understand > this makes no difference for the repo code, but still a bit confusing > for me. The problem here is that Git understands something different from what you intended: if you say `git checkout `, Git is mostly interested in the revision, i.e. the commit. Only if that parameter refers to a local branch name (which is the only type of ref Git expects to advance via the worktree) does it switch to a named branch. Otherwise it switches to what I like to call "unnamed branch" (and which for historical reasons is called "detached HEAD" by Git, something that is unlikely to be understood without explicit explanation). Now, as a convenience, Git tries to name the revision when it is on such an unnamed branch. If a tag points to it, it uses the name of that tag to describe it. If *multiple* tags point to it, it uses the newest one. That's why you see what you see. It is intended behavior... Ciao, Johannes
Re: Possible bug report
Pierre-François CLEMENT lik...@gmail.com writes: As you can see, the --cumulative lines seem to be duplicated, though the computed stats aren't exactly the same... It appears when you combine the --cumulative option with either --stat, --numstat or --shortstat (but not --dirstat) ... Thanks for a report. I do not think the deprecated --cumulative command line option was ever designed to be used with anything but --dirstat. It was a UI mistake to make it look like an independent option, which was corrected with 333f3fb0c530 (Refactor --dirstat parsing; deprecate --cumulative and --dirstat-by-file, 2011-04-29) and the fix shipped back in v1.7.6. Since that release we do not even mention the option in the manual. These days, the right way to spell it is as an option parameter to the --dirstat option itself (e.g. --dirstat=cumulative). The parser to parse --cumulative as a command line argument was kept so that people who were used to --dirstat --cumulative do not have to see an error from the command line parser. We could have made --cumulative with other kind of stat an error back then, but we didn't. I suspect that we thought it would be sufficient to not document --cumulative as a standalone option, but I do not recall the details. -- 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