git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Pushing a single tag (ref + object)?
       [not found] <46a038f90510131929m3dac4cc5y6071550e9e9c71ad@mail.gmail.com>
@ 2005-10-19  6:05 ` Martin Langhoff
  2005-10-19 12:39   ` Horst von Brand
  2005-10-19 14:13   ` Linus Torvalds
  0 siblings, 2 replies; 5+ messages in thread
From: Martin Langhoff @ 2005-10-19  6:05 UTC (permalink / raw)
  To: Git Mailing List

While we are using a repo which holds all our branches
(dev/test/prod), locally we have a group of developers that checkout
one repo-per-branch, working on it with a
cg-clone/cg-update/cg-commit/cg-push workcycle. So far it's working
great.

Now, I am at a loss on how to push a _tag_ object+ref to the repo,
without doing a git-push --all, which I naturally don't want to do. I
managed to push the object itself, doing

    git-push repository tagrefname

But that ddn't create the ref on the repo. So I had to do

    scp .git/refs/tags/refname repostory/refs/tags/

I'm feeling a tad lost here. Surely there's a way? Or should I be
crafting a patch against git-push-script? Problem is, git-push script
doesn't do any parsing of the params. Grmbl.


martin

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Pushing a single tag (ref + object)?
  2005-10-19  6:05 ` Pushing a single tag (ref + object)? Martin Langhoff
@ 2005-10-19 12:39   ` Horst von Brand
  2005-10-19 14:13   ` Linus Torvalds
  1 sibling, 0 replies; 5+ messages in thread
From: Horst von Brand @ 2005-10-19 12:39 UTC (permalink / raw)
  To: Martin Langhoff; +Cc: Git Mailing List

Martin Langhoff <martin.langhoff@gmail.com> wrote:
> While we are using a repo which holds all our branches
> (dev/test/prod), locally we have a group of developers that checkout
> one repo-per-branch, working on it with a
> cg-clone/cg-update/cg-commit/cg-push workcycle. So far it's working
> great.
> 
> Now, I am at a loss on how to push a _tag_ object+ref to the repo,
> without doing a git-push --all, which I naturally don't want to do. I
> managed to push the object itself, doing
> 
>     git-push repository tagrefname
> 
> But that ddn't create the ref on the repo. So I had to do
> 
>     scp .git/refs/tags/refname repostory/refs/tags/

I've done:

     git push repository refs/tags/refname
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Pushing a single tag (ref + object)?
  2005-10-19  6:05 ` Pushing a single tag (ref + object)? Martin Langhoff
  2005-10-19 12:39   ` Horst von Brand
@ 2005-10-19 14:13   ` Linus Torvalds
  2005-10-19 16:58     ` Junio C Hamano
  1 sibling, 1 reply; 5+ messages in thread
From: Linus Torvalds @ 2005-10-19 14:13 UTC (permalink / raw)
  To: Martin Langhoff, Junio C Hamano; +Cc: Git Mailing List



On Wed, 19 Oct 2005, Martin Langhoff wrote:
> 
> Now, I am at a loss on how to push a _tag_ object+ref to the repo,
> without doing a git-push --all, which I naturally don't want to do. I
> managed to push the object itself, doing
> 
>     git-push repository tagrefname

This really should work. 

Can you try with

	git-send-pack repository tagname

first? 

If that works for you (it really really should, since that's what I do all 
the time), then the problem is in "get_remote_refs_for_push"..

Oh. Looking at "git-push.sh", I think it is just really really buggy.

It does all this magic to set "x", but then it never uses it, and uses 
"$@" instead after all. Which it has shifted all away. 

How does that thing work at all? Me, I've always used the raw 
git-send-pack program, so I've never tested it, but obviously others are 
using it.

		Linus

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Pushing a single tag (ref + object)?
  2005-10-19 14:13   ` Linus Torvalds
@ 2005-10-19 16:58     ` Junio C Hamano
  2005-10-19 20:23       ` Linus Torvalds
  0 siblings, 1 reply; 5+ messages in thread
From: Junio C Hamano @ 2005-10-19 16:58 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: git

Linus Torvalds <torvalds@osdl.org> writes:

> It does all this magic to set "x", but then it never uses it, and uses 
> "$@" instead after all. Which it has shifted all away. 

Your /bin/sh scripting is rotting ;-) That is not a variable.
If you saw the script actually used the value 'x' then you have
spotted a bug.

That 'x' is not a magic but an old idiom to protect 'set' from
getting confused by "$1" that happens to begin with a '-'.
Setting random things is done by "set x random things"
immediately followed by shifting that x away.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Pushing a single tag (ref + object)?
  2005-10-19 16:58     ` Junio C Hamano
@ 2005-10-19 20:23       ` Linus Torvalds
  0 siblings, 0 replies; 5+ messages in thread
From: Linus Torvalds @ 2005-10-19 20:23 UTC (permalink / raw)
  To: Junio C Hamano; +Cc: git



On Wed, 19 Oct 2005, Junio C Hamano wrote:
> 
> Your /bin/sh scripting is rotting ;-) That is not a variable.

Ahh. No. My /bin/sh scripting just has never been that good to begin with, 
since there's little reason to do so inside the kernel ;)

I literally didn't understand what "set" does. Thx. man-pages to the 
rescue.

		Linus

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2005-10-19 20:23 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <46a038f90510131929m3dac4cc5y6071550e9e9c71ad@mail.gmail.com>
2005-10-19  6:05 ` Pushing a single tag (ref + object)? Martin Langhoff
2005-10-19 12:39   ` Horst von Brand
2005-10-19 14:13   ` Linus Torvalds
2005-10-19 16:58     ` Junio C Hamano
2005-10-19 20:23       ` Linus Torvalds

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).