On 06/11/2014 12:21 PM, Wojciech Przybył wrote:
When I was tagging, I think I might have discovered a git client bug.
[...]
HOW TO REPRODUCE:
- Clone a repo into 2 separate directories. Presume there is a tag
v0.1 already in there and it is set on say 10 commits ago.
- In first directory
Hi
Thanks, it's exactly what I was after.
BTW
Just looking at ubuntu packages (I was using 12.04LTS) and it looks
like in a recent LTS release (14.04LTS) they still have git version
1.9.1, and only on utopic ubuntu (the newest one) git is 2.0.0.
Anyway, it's probably good time to upgrade.
Many
Hi All
When I was tagging, I think I might have discovered a git client bug.
HOW TO REPRODUCE:
- Clone a repo into 2 separate directories. Presume there is a tag
v0.1 already in there and it is set on say 10 commits ago.
- In first directory change the tag to a different place and push it
to
On 11.06.2014 12:21, Wojciech Przybył wrote:
Hi All
When I was tagging, I think I might have discovered a git client bug.
HOW TO REPRODUCE:
- Clone a repo into 2 separate directories. Presume there is a tag
v0.1 already in there and it is set on say 10 commits ago.
- In first directory
Hi
Thanks for your quick reply. Just read the link and I agree it is not
the right thing to do, especially when someone else has already picked
up the tag. In such case, I fully agree, the developer should say I
messed up, sorry.
Simultaneously, once such situation occurs, I think git should not
5 matches
Mail list logo