# Re: Pushing a single tag (ref + object)? 4 messages from 2005-10-19 to 2005-11-02. Participants: Horst von Brand, Andreas Ericsson, Junio C Hamano. Thread: https://gitlist.dev/t/2150 ## Horst von Brand, 2005-10-19 12:39 Subject: Re: Pushing a single tag (ref + object)? Message-ID: <200510191239.j9JCd5nQ018754@laptop11.inf.utfsm.cl> URL: https://gitlist.dev/e/200510191239.j9JCd5nQ018754%40laptop11.inf.utfsm.cl In-Reply-To: ``` Martin Langhoff 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 ``` ## Horst von Brand, 2005-11-01 23:56 Subject: Re: git versus CVS (versus bk) Message-ID: <200511012356.jA1NuPBd004502@inti.inf.utfsm.cl> URL: https://gitlist.dev/e/200511012356.jA1NuPBd004502%40inti.inf.utfsm.cl In-Reply-To: ``` Martin Langhoff wrote: [...] > In practice, a new developer will often roll up commits to avoid > sending a string of shameful patches and corrections on top -- I often > do that ;-) . Developers with more "mana" will have published repos > where Junio pulls directly from -- and they get merged with full > history. Of course -- they don't have brown-paper-bag commits like I > do... I bet they have a scratchpad on their laptop (full of brown-paper-bag commits and backtracking) from which they push into a cleaned up repository for public consumption. -- 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 ``` ## Andreas Ericsson, 2005-11-02 08:54 Subject: Re: git versus CVS (versus bk) Message-ID: <43687EAF.4060505@op5.se> URL: https://gitlist.dev/e/43687EAF.4060505%40op5.se In-Reply-To: <200511012356.jA1NuPBd004502@inti.inf.utfsm.cl> ``` Horst von Brand wrote: > Martin Langhoff wrote: > > [...] > > >>In practice, a new developer will often roll up commits to avoid >>sending a string of shameful patches and corrections on top -- I often >>do that ;-) . Developers with more "mana" will have published repos >>where Junio pulls directly from -- and they get merged with full >>history. Of course -- they don't have brown-paper-bag commits like I >>do... > > > I bet they have a scratchpad on their laptop (full of brown-paper-bag > commits and backtracking) from which they push into a cleaned up repository > for public consumption. I just do a lot of branches. Incidentally though, is there any way to make a commit completely go away without resetting the files? It'd be a nice feature even if it can only do it from the top down, unlike git-revert which can do it anywhere in the middle as well. -- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 ``` ## Junio C Hamano, 2005-11-02 09:26 Subject: Re: git versus CVS (versus bk) Message-ID: <7v8xw7v1r0.fsf@assigned-by-dhcp.cox.net> URL: https://gitlist.dev/e/7v8xw7v1r0.fsf%40assigned-by-dhcp.cox.net In-Reply-To: <43687EAF.4060505@op5.se> ``` Andreas Ericsson writes: > Incidentally though, is there any way to make a commit completely go > away without resetting the files? I am not sure if this is what you are looking for, but after I make a commit and find a mistake (either in the checked-in files or commit log message), I do this: $ git reset --soft HEAD^ ... fix the checked-in files, maybe do git-add files that ... I forgot to add when I made the last commit. $ git commit -a -c ORIG_HEAD ;# edit commit log, too. Soft reset leaves the working tree files intact and just rewinds the .git/HEAD to whatever commit you specify, and as a side effect stores the original .git/HEAD in .git/ORIG_HEAD. The lowercase -c flag to git-commit is "bring the commit log editor, initialized with the commit log message from that commit". ```