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

Re: [PATCH] README: Sketch out what tg rename OLD NEW would do.

From
Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Date
Feb 28, 2010, 10:13 UTC
Message-ID
<20100228101320.GA13987@pengutronix.de>
In-Reply-To
<1267310389-11984-1-git-send-email-thomas@schwinge.name>
Hello Thomas,
On Sat, Feb 27, 2010 at 11:39:49PM +0100, Thomas Schwinge wrote:
Show 21 quoted lines
> ... as proposed by me and acknowledged by David Bremner and Uwe Kleine-König on
> 2010-01-27 in #topgit (freenode).
> ---
>  README |   17 ++++++++++++++++-
>  1 files changed, 16 insertions(+), 1 deletions(-)
> 
> diff --git a/README b/README
> index 495c70b..eab6fcd 100644
> --- a/README
> +++ b/README
> @@ -486,7 +486,22 @@ tg push
>  	repository.  By default the remote gets all dependencies
>  	(both tgish and non-tgish) and bases pushed to.
>  
> -TODO: tg rename
> +tg rename
> +~~~~~~~~~
> +	There is no such command yet, but here's a receipe what ``tg rename OLD
> +	NEW'' would do:
> +
> +	  - Have a clean state before beginning.
- assert NEW doesn't already exist?
> +	  - git banch -r OLD NEW
s/banch/branch/
Show 12 quoted lines
> +	  - git update-ref refs/top-bases/NEW refs/top-bases/OLD ''
> +	  - for BRANCH in (all branches that depend on OLD,
> +			   i.e. reference OLD in .topdeps); do
> +	      git checkout BRANCH
> +	      sed -i 's%^OLD$%NEW$' .topdeps
> +	      git commit -m 'OLD -> NEW' .topdeps
> +	    done
> +	  - tg summary
> +	  - tg update as appropriate
>  
>  
>  IMPLEMENTATION
Otherwise looks OK

Best regards Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Previous: Thomas SchwingeNext: Thomas Schwinge
Message 2 of 3 in “README: Sketch out what tg rename OLD NEW would do.”
  1. README: Sketch out what tg rename OLD NEW would do.Thomas Schwinge, Feb 27, 2010
  2. Uwe Kleine-KönigFeb 28, 2010
  3. README: Sketch out what tg rename OLD NEW would do.Thomas Schwinge, Feb 28, 2010

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.