Re: best git practices, was Re: Git User's Survey 2007 unfinished summary continued

From: J. Bruce Fields <bfields@fieldses.org>
Date: Oct 24, 2007, 22:38 UTC
Message-ID: <20071024223815.GN29830@fieldses.org>
In-Reply-To: <008A7EF9-6F58-47AE-9AA0-B466797F6B1D@zib.de>

On Thu, Oct 25, 2007 at 12:33:37AM +0200, Steffen Prohaska wrote:

> Maybe. I know git quite well now and in a shared workflow "git pull"
> with auto-fast-forward would help me. I often need to run "for each
> local branch: git checkout ; git merge" to get rid of the errors
> reported by "git push".

Hm. There's gotta be more efficient ways to do that. Maybe "git push . origin/branch:branch" for each local "branch"?

But I'm still a little confused why you don't just want to "git push name-of-branch" and avoid the whole problem.

--b.

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