On Thu, May 23, 2013 at 02:19:40PM -0700, Junio C Hamano wrote:
> "Michael S. Tsirkin" writes:
>
> > On Thu, May 23, 2013 at 11:05:00AM -0700, Junio C Hamano wrote:
> >> "Michael S. Tsirkin" writes:
> >>
> >> > Looks like push can't resolve tags to commits.
> >> > Why is that?
> >>
> >> How el
"Michael S. Tsirkin" writes:
> It's a tag and not a branch since I need to sign the tag.
> I push to a branch and not just the tag since this way
> people can track it and do downstream development on top.
> So pushing the tag to branch would save me some churn.
It seems our messages crossed.
E
"Michael S. Tsirkin" writes:
> On Thu, May 23, 2013 at 11:05:00AM -0700, Junio C Hamano wrote:
>> "Michael S. Tsirkin" writes:
>>
>> > Looks like push can't resolve tags to commits.
>> > Why is that?
>>
>> How else would you push a tag out?
>
> Well my reaction is, it seems to figure out it ne
On Thu, May 23, 2013 at 11:10:32AM -0700, Junio C Hamano wrote:
> Felipe Contreras writes:
>
> > On Thu, May 23, 2013 at 5:53 AM, Michael S. Tsirkin wrote:
> >> Looks like push can't resolve tags to commits.
> >> Why is that?
> >>
> >> linux$ git push -f $PWD v3.10-rc2:refs/heads/vhost-next
> >
On Thu, May 23, 2013 at 11:05:00AM -0700, Junio C Hamano wrote:
> "Michael S. Tsirkin" writes:
>
> > Looks like push can't resolve tags to commits.
> > Why is that?
>
> How else would you push a tag out?
Well my reaction is, it seems to figure out it needs a commit and then
instead of just gett
"Michael S. Tsirkin" writes:
> On Thu, May 23, 2013 at 11:10:32AM -0700, Junio C Hamano wrote:
>> Felipe Contreras writes:
>>
>> > On Thu, May 23, 2013 at 5:53 AM, Michael S. Tsirkin
>> > wrote:
>> >> Looks like push can't resolve tags to commits.
>> >> Why is that?
>> >>
>> >> linux$ git pus
On Thu, May 23, 2013 at 11:10:32AM -0700, Junio C Hamano wrote:
> Felipe Contreras writes:
>
> > On Thu, May 23, 2013 at 5:53 AM, Michael S. Tsirkin wrote:
> >> Looks like push can't resolve tags to commits.
> >> Why is that?
> >>
> >> linux$ git push -f $PWD v3.10-rc2:refs/heads/vhost-next
> >
Felipe Contreras writes:
> On Thu, May 23, 2013 at 5:53 AM, Michael S. Tsirkin wrote:
>> Looks like push can't resolve tags to commits.
>> Why is that?
>>
>> linux$ git push -f $PWD v3.10-rc2:refs/heads/vhost-next
>
> Perhaps v3.10-rc2^{}. Yeah, totally and completely not-user-friendly,
More co
"Michael S. Tsirkin" writes:
> Looks like push can't resolve tags to commits.
> Why is that?
How else would you push a tag out?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/m
On Thu, May 23, 2013 at 5:53 AM, Michael S. Tsirkin wrote:
> Looks like push can't resolve tags to commits.
> Why is that?
>
> linux$ git push -f $PWD v3.10-rc2:refs/heads/vhost-next
Perhaps v3.10-rc2^{}. Yeah, totally and completely not-user-friendly,
I already complained about it to no avail.
On Thu, May 23, 2013 at 01:53:10PM +0300, Michael S. Tsirkin wrote:
> Looks like push can't resolve tags to commits.
> Why is that?
>
> linux$ git push -f $PWD v3.10-rc2:refs/heads/vhost-next
> error: Trying to write non-commit object
> a8c6d53c4d84b3a5eb182758a9cdceceba4691da to branch refs/heads
Looks like push can't resolve tags to commits.
Why is that?
linux$ git push -f $PWD v3.10-rc2:refs/heads/vhost-next
error: Trying to write non-commit object
a8c6d53c4d84b3a5eb182758a9cdceceba4691da to branch refs/heads/vhost-next
To /scm/linux
! [remote rejected] v3.10-rc2 -> vhost-next (failed t
12 matches
Mail list logo
