On May 20, 4:10 am, David Aguilar <[email protected]> wrote: > Maybe not a huge deal, but you do lose the ability to do: > > % git describe --match='v*'
That's an interesting point. Although it precludes naming a tag starting with the letter 'v' unless it is in fact a version. Is it not possible to use a regular expression '\d.*' ? > It's just a convention, but not a bad one. If you consider > that later you might imagine a new use for tags, then using > a convention today allows scripts to protect themselves by > only considering the "v" tags. > > Many large projects use this convention, too. > Consistency never hurts, especially for mundane stuff > like tag naming ;-) True true. I just decide the convention would be v#.#.#, OR #.#.# ;-) > David > > [1] - Maybe they all just copied Linus? Yea. I would not be surprised if that is the case. I noticed the same thing with people putting their project's website file in a naked branch, which I find to be a pain in the butt. What's wrong with a subdirectory? I asked that very question of the GitHub people because this is what they do with the gh-pages branch. Guess what they said? -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
