On Mon, Mar 25, 2019 at 08:19:25PM +0100, Ævar Arnfjörð Bjarmason wrote:
> > $ git tag -a mytag
> > error: refusing to make a recursive tag
> > hint: The object 'mytag' referred to by your new tag is already a tag.
> > hint:
> > hint: If you meant to create a tag of a tag, use:
> > hin
On Mon, Mar 25, 2019 at 11:43:52AM -0700, Bryan Turner wrote:
> > I don't think I've ever seen a tag-to-a-tag in the wild, but I wouldn't
> > be surprised if somebody has found a use for it. For example, because
> > tags can be signed, I can make a signature of your signature, showing a
> > crypto
On Mon, Mar 25 2019, Jeff King wrote:
> On Mon, Mar 25, 2019 at 08:50:14AM -0500, Robert Dailey wrote:
>
>> On Thu, Mar 21, 2019 at 2:29 PM Jeff King wrote:
>> > Tags can point to any object, including another tag. It looks like
>> > somebody made an annotated tag of an annotated tag (probably
On Mon, Mar 25, 2019 at 7:49 AM Jeff King wrote:
>
> On Mon, Mar 25, 2019 at 08:50:14AM -0500, Robert Dailey wrote:
>
> > On Thu, Mar 21, 2019 at 2:29 PM Jeff King wrote:
> > > Tags can point to any object, including another tag. It looks like
> > > somebody made an annotated tag of an annotated
On Mon, Mar 25, 2019 at 9:49 AM Jeff King wrote:
> I think "just commits" is too restrictive. linux.git contains a tag of a
> tree, for example (we also have tags pointing to blobs in git.git, but
> they are not annotated).
>
> However, I could see an argument for the git-tag porcelain to notice a
On Mon, Mar 25, 2019 at 08:50:14AM -0500, Robert Dailey wrote:
> On Thu, Mar 21, 2019 at 2:29 PM Jeff King wrote:
> > Tags can point to any object, including another tag. It looks like
> > somebody made an annotated tag of an annotated tag (probably by
> > mistake, given that they have the same t
On Thu, Mar 21, 2019 at 2:29 PM Jeff King wrote:
> Tags can point to any object, including another tag. It looks like
> somebody made an annotated tag of an annotated tag (probably by
> mistake, given that they have the same tag-name).
>
> Try this:
>
> git init
> git commit -m commit --allow-
On Thu, Mar 21, 2019 at 12:04:22PM -0700, Bryan Turner wrote:
> > Why does it show two entries? In my `packed-refs` file, it also shows
> > a strange revision for the tag (I expect to see just 1 SHA1). Not sure
> > if it is related:
> >
> > ```
> > 66c41d67da887025c4e22e9891f5cd261f82eb31 refs/tag
On Thu, Mar 21, 2019 at 11:59:42AM -0500, Robert Dailey wrote:
> I have a particular tag in my repo that shows 2 annotated
> descriptions, which is very confusing.
>
> The command I ran:
>
> ```
> git show --format=fuller 4.2.0.1900
> ```
>
> And the output:
>
> ```
> tag 4.2.0/1900
> Tagger:
On Thu, Mar 21, 2019 at 9:59 AM Robert Dailey wrote:
>
> I have a particular tag in my repo that shows 2 annotated
> descriptions, which is very confusing.
>
> The command I ran:
>
> ```
> git show --format=fuller 4.2.0.1900
> ```
>
> And the output:
>
> ```
> tag 4.2.0/1900
> Tagger: John Doe
I have a particular tag in my repo that shows 2 annotated
descriptions, which is very confusing.
The command I ran:
```
git show --format=fuller 4.2.0.1900
```
And the output:
```
tag 4.2.0/1900
Tagger: John Doe
TaggerDate: Fri Jul 18 10:46:30 2014 -0500
QA/Internal Release for 4.2.0.19
11 matches
Mail list logo
