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

Re: [PATCH] Use non-interactive function to byte-compile files

From
Karl Hasselström <kha@treskal.com>
Date
Mar 5, 2007, 15:04 UTC
Message-ID
<20070305150418.GD3481@diana.vm.bytemark.co.uk>
In-Reply-To
<Pine.LNX.4.63.0703051554240.22628@wbgn013.biozentrum.uni-wuerzburg.de>
On 2007-03-05 15:54:46 +0100, Johannes Schindelin wrote:
Show 6 quoted lines
> On Mon, 5 Mar 2007, Karl Hasselström wrote:
>
> > Yes, Documentation/SubmittingPatches is a loooong text ...
>
> Unless you count all the MUA specific things, it is just 162
> lines...

There's still a lot of information in there. It's not hard to forget one out of the ~28 paragraphs of non-MUA-specific info.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 4 of 8 in “Use non-interactive function to byte-compile files”
  1. Use non-interactive function to byte-compile filesXavier Maillard, Mar 5, 2007
  2. Karl HasselströmMar 5, 2007
  3. Johannes SchindelinMar 5, 2007
  4. Karl HasselströmMar 5, 2007
  5. Begin SubmittingPatches with a check listJohannes Schindelin, Mar 5, 2007
  6. Alex RiesenMar 5, 2007
  7. Brian GernhardtMar 5, 2007
  8. Johannes SchindelinMar 5, 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.