From: Michael Witten <mfwitten@gmail.com>
To: "John S. Urban" <urbanjost@comcast.net>
Cc: git@vger.kernel.org
Subject: Lost association between TAGS and COMMITs when rebased a git(1) repository
Date: Sun, 04 Sep 2011 14:03:12 -0000 [thread overview]
Message-ID: <3c10d6593152436c9dd3a5b5773e3c79-mfwitten@gmail.com> (raw)
In-Reply-To: <FF0364F3D5244CA4987EDDCFE7244BF3@urbanjsPC>
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@mail.gmail.com>
http://article.gmane.org/gmane.comp.version-control.git/179942
Message-ID: <CAMOZ1Bti3ZtAEOtLiUYSkWE+rO_VQd09NAn58Cn4hZBu8f-aFQ@mail.gmail.com>
next prev parent reply other threads:[~2011-09-04 14:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 1:32 Lost association between TAGS and COMMITs when rebased a git(1) repository John S. Urban
2011-09-04 10:02 ` PJ Weisberg
2011-09-04 13:40 ` Michael Witten
2011-09-04 14:03 ` Michael Witten [this message]
[not found] ` <CA+sFfMcMgPDyCi6SCS=Sc4XFrug_Ee7vbmBBkmkwfwwpXg8yCg@mail.gmail.com>
2011-09-04 14:38 ` Michael Witten
2011-09-04 17:20 ` Philip Oakley
2011-09-04 18:15 ` knittl
2011-09-04 14:30 ` knittl
2011-09-04 14:43 ` Michael Witten
2011-09-04 15:39 ` Jakub Narebski
2011-09-04 18:16 ` Tor Arntsen
2011-09-04 18:43 ` Thomas Rast
2011-09-04 19:11 ` Tor Arntsen
2011-09-04 20:18 ` John S. Urban
2011-09-04 20:28 ` [PATCH] Documentation: "on for all" configuration of notes.rewriteRef Thomas Rast
2011-09-04 20:43 ` Tor Arntsen
2011-09-07 21:23 ` Jeff King
2011-09-07 21:29 ` Thomas Rast
2011-09-07 21:35 ` Jeff King
[not found] ` <CACx-yZ1Ce3x=ZSdm5iY3JqYjVGVs5uPnb12-tMJP7zWsGuMK_Q@mail.gmail.com>
2011-09-04 16:40 ` Lost association between TAGS and COMMITs when rebased a git(1) repository John S. Urban
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3c10d6593152436c9dd3a5b5773e3c79-mfwitten@gmail.com \
--to=mfwitten@gmail.com \
--cc=git@vger.kernel.org \
--cc=urbanjost@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).