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

Re: Question on git fetch to bare repo

From
Jeff King <peff@peff.net>
Date
Feb 13, 2007, 05:31 UTC
Message-ID
<20070213053103.GA3795@coredump.intra.peff.net>
In-Reply-To
<7vejou39ud.fsf@assigned-by-dhcp.cox.net>
On Mon, Feb 12, 2007 at 09:28:10PM -0800, Junio C Hamano wrote:
Show 7 quoted lines
> One solution would be to list only the new commits introduced by
> the push into the repository, regardless of the branch.  You can
> replace the "git-shortlog $old..$new" with:
> 
> 	git shortlog $new --not --all
> 
> to get that information, I think.

I don't think that addresses his concern. I had suggested to him that he do all pulling/merging in his private repo, then simply keep the public repo as a mirror. In that case, when pushing out to the public repo, _all_ commits will likely be new to the public repo, including those ones that he pulled from elsewhere.

-Peff
Previous: Junio C Hamano
Message 10 of 10 in “Question on git fetch to bare repo”
  1. Bill LearFeb 8, 2007
  2. Jakub NarebskiFeb 8, 2007
  3. Johannes SchindelinFeb 9, 2007
  4. Johannes SchindelinFeb 9, 2007
  5. Jeff KingFeb 9, 2007
  6. Bill LearFeb 9, 2007
  7. Bill LearFeb 12, 2007
  8. Jeff KingFeb 13, 2007
  9. Junio C HamanoFeb 13, 2007
  10. Jeff KingFeb 13, 2007

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.