On Sat, 3 Sep 2011 21:32:03 -0400, John S. Urban wrote: > With my first use of git(1) I created a small project with about 200 > "commits". When this was complete, I needed to label each commit with > information pointing it to a section of a document. What exactly does that mean? > I used tags for this. It sounds like `git notes' or rewritten commit messages would be what is appropriate. > So far, everything was fine. I was then asked to merge two commits > into one. I then did a "rebase" (for the first time). You mean `squash'; the term `merge' has a specific meaning in git nomenclature. > Also, I have some commits with multiple tags pointing to them. It has come > to my attention that might not be an intentional feature. I could find > nothing in the documentation explicitly stating multiple tags were allowed > to point to a commit; but the tags seem to be unique "objects" so I > see no reason this should not be an expected feature? Well, everybody, it sounds like John's confusion is a good example for why `tag' is another TERRIBLE choice of terminology. See here: http://article.gmane.org/gmane.comp.version-control.git/179609 Message-ID: <CAMOZ1Btmk86vmp1gRuCfG7yRuc6fD3_oYBvtq2VKK9Ywu8ay0A@xxxxxxxxxxxxxx> http://article.gmane.org/gmane.comp.version-control.git/179942 Message-ID: <CAMOZ1Bti3ZtAEOtLiUYSkWE+rO_VQd09NAn58Cn4hZBu8f-aFQ@xxxxxxxxxxxxxx> -- 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