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

Re: [RFC] git-publish

From
Sam Ravnborg <sam@ravnborg.org>
Date
Aug 13, 2006, 20:41 UTC
Message-ID
<20060813204118.GA21956@mars.ravnborg.org>
In-Reply-To
<Pine.LNX.4.64.0608131536590.9789@iabervon.org>
On Sun, Aug 13, 2006 at 04:11:32PM -0400, Daniel Barkalow wrote:
Show 10 quoted lines
> On Sun, 13 Aug 2006, Sam Ravnborg wrote:
> 
> > But important note is that publishing is something I defer until some
> > limited test has been done. And when I omit that I have always ended u
> > pushing some crappy stuff that needs to be dealt with.
> 
> I also test before publishing. But I test before committing, too, because 
> I never get anything right (or even logically complete) the first time. My 
> cycle is edit/build/test, and if the test is successful, I commit and 
> push.

It happens that I discover bugs while working on next issue. And sometime I get my light moments after commiting a patch.

Obviously I test before commit.
	Sam
Previous: Daniel BarkalowNext: Alex Riesen
Message 8 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.