git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Questions on 'cvs migration guide''

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Aug 19, 2005, 05:58 UTC
Message-ID
<46a038f9050818225865deb7ee@mail.gmail.com>
In-Reply-To
<Pine.LNX.4.58.0508182130050.3412@g5.osdl.org>
On 8/19/05, Linus Torvalds <torvalds@osdl.org> wrote:
Show 8 quoted lines
> > And yet another question: the teammember who is pulling must 'switch'
> > the merging repo to the right branch, pull from the corresponding
> > remote repos of each teammember, and push to the public view of the
> > repo. Is that right?
> 
> .. yes. Or alternatively, just keep the repo at that branch (and if such a
> person works on multiple branches, he/she can thus just keep multiple
> repos).

I'm keen on keeping my 'merge & publish' step in a single repo that has all the 'team' branches. The person running this repo will probably actually code in separate repos, and merge in there too.

Right now I'm switching 'heads' (I'm getting used to cogito's use of 'branch' for 'remote head') using this quick'n'dirty bit of shell:

#!/bin/bash 
HEADNAME=$1
if [ -e .git/refs/heads/$HEADNAME ]; then
	cd .git/
	ln -s -f .git/refs/heads/$HEADNAME HEAD
	cd ..
	cg-reset
	cg-restore -f
fi;

but I want to prevent the action if the checkout is 'dirty'. Is there any way to check whether cg-diff thinks anything has changed?

cheers,
martin
Previous: Linus TorvaldsNext: Linus Torvalds
Message 3 of 4 in “Questions on 'cvs migration guide''”
  1. Martin LanghoffAug 19, 2005
  2. Linus TorvaldsAug 19, 2005
  3. Martin LanghoffAug 19, 2005
  4. Linus TorvaldsAug 19, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.