How about one of these: refish shaish commitish treeish
Actually, "treeish" or commitish might be best -- you want to specify the state of a directory tree, and you are probably using something that identifies a commit, which identifies a tree plus a message. On 2018-11-26, at 7:20 AM, Philip Oakley <philipoak...@iee.org> wrote: > This time from my correct email address... > > -------- Forwarded Message -------- > Subject: Re: [git-users] Collective noun for Git branch, tag, or revision > Date: Mon, 26 Nov 2018 14:59:47 +0000 > From: Philip Oakley <philipoakley@xx > To: email@example.com, Ilya Vassilevsky <vassilev...@gmail.com> > > > > Hi Ily, > > I think the technically correct term is 'reference' but, you would be right, > that it is very confusing. i.e. those items in the `refs/` directory see > <refname>  > > e.g. my > https://stackoverflow.com/questions/11792538/in-git-what-is-the-difference-between-a-commits-and-a-revisions > > The distinction [for you?] should be between the object types you can > "compile and deploy". If you can "compile and deploy" a tree, then you have > probably dug a hole in which to bury the terminology. > > If the only things you want to "compile and deploy" are only commits, then it > is easier and more consistently a reference (but still not perfectly). > > In the Git history there is (IIRC) a tag (a mistake by Linus of all people!) > that actually tags a tree, rather than a commit. This means that tags can > reference other objects of a type you may not want to allow! > > The other problem is a raw sha1 (oid) value (given as a string) can be a > 'reference', and has the same multi-way object type designation issue. > > I think you end up with allowing "commits and references to commits". > > Philip > PS try 'git help revisions' to see the guide > https://git-scm.com/docs/gitrevisions > >  > https://git-scm.com/docs/gitrevisions#gitrevisions-emltrefnamegtemegemmasterememheadsmasterememrefsheadsmasterem > (just how they created that section link I don't want to know ;-) > > On 26/11/2018 14:20, Ilya Vassilevsky wrote: >> Hello everyone :) >> >> I'm developing a deployment automation tool. It can compile and deploy code >> from a Git repository. >> >> I would like to add a command-line argument that specifies the revision to >> deploy. It can be a branch name, a tag name, or just a plain SHA-1. >> >> What is the best collective noun for these? >> >> "Revision" does not cover branches and tags. "Reference" does not cover >> revisions. "From" is a good candidate :) but I would like to use something >> more Git-specific. >> >> Thanks! >> -- You received this message because you are subscribed to the Google Groups >> "Git for human beings" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to git-users+unsubscr...@googlegroups.com >> <mailto:git-users+unsubscr...@googlegroups.com>. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Git for human beings" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. --- Entertaining minecraft videos http://YouTube.com/keybounce -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.