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

Re: [RFC] git-publish

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Aug 13, 2006, 18:20 UTC
Message-ID
<Pine.LNX.4.63.0608132017090.10541@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<Pine.LNX.4.64.0608131158500.9789@iabervon.org>
Hi,
On Sun, 13 Aug 2006, Daniel Barkalow wrote:
> Like how "pull" is "fetch" + "merge", I think it would be useful to have 
> a "commit" + "push".

I found myself the other day, looking for files I committed on a box which was 280 kilometer away, where I forgot to push. So I understand your feeling.

However, adding to Junio's arguments, I find it saner to keep them separated: you should commit _often_. Way more often than you would need to push. There are many reasons, why small patches are more beautiful than big ones, and git actually encourages you to make small patches.

I'd rather have a command which tells me if I have commits after the last time I pushed.

Ciao, Dscho

Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 14 in “[RFC] git-publish”
  1. Daniel BarkalowAug 13, 2006
  2. Junio C HamanoAug 13, 2006
  3. Johannes SchindelinAug 13, 2006
  4. Junio C HamanoAug 13, 2006
  5. Sam RavnborgAug 13, 2006
  6. Fredrik KuivinenAug 13, 2006
  7. Daniel BarkalowAug 13, 2006
  8. Sam RavnborgAug 13, 2006
  9. Alex RiesenAug 14, 2006
  10. Shawn PearceAug 14, 2006
  11. Junio C HamanoAug 14, 2006
  12. Jeff KingAug 14, 2006
  13. Martin LanghoffAug 13, 2006
  14. Petr BaudisSep 24, 2006

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.