My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1823: repo: repo sync should use the tag name instead of object identifier of the tag
1 person starred this issue and may be notified of changes. Back to list
Status:  Invalid
Owner:  ----
Closed:  Mar 2013


Sign in to add a comment
 
Reported by yann@droneaud.fr, Mar 12, 2013
Hi,

After updating a manifest project revision, switching from a previous tag (v1.12.1) to a newer tag (v1.12.2) on the same branch, repo sync makes git merge (by recursive method) the newer tag into the local repository. In this case, git spawn an editor to create a merge commit message.

In this case, the default commit message is about merging the object identifier (ac22c7ae2e652f63366b65ee23122292d3564fff) instead of the newer tag (v1.12.2) making it hard to understand what's get updated/merged. Additionally ac22c7ae2e652f63366b65ee23122292d3564fff is the object identifier of the tag (signed) while the first commit to be merged will be 45d21685b93f80b67239849b2d2cfe6b217e335a instead, which is very disappointing.

Additionally, when the tag name is used, git will check the PGP/GPG signature of the signed tag. It doesn't happen when the object identifier of the signed tag is used.

This problem happen when the tag to be merged is a signed/annotated tag, eg it's an object with an identifier. 
This doesn't happen when a branch or a tag reference/lightweight tag is to be merged: a fast-forward merge is done and no merge commit is created.

repo sync should use the tag name (reference) to do the merge and not the object identifier.



Mar 12, 2013
Project Member #1 bklarson@gmail.com
I believe repo issues should be reported at https://code.google.com/p/git-repo/.  This issue tracker is only for Gerrit.
Status: Invalid
Sign in to add a comment

Powered by Google Project Hosting