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

Re: [PATCH] Makefile: add CC to TRACK_CFLAGS

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Sep 20, 2010, 13:38 UTC
Message-ID
<AANLkTikLCFb3GrMxP7dLPB=eggc2w6FOq=7ZpdSYpnki@mail.gmail.com>
In-Reply-To
<7viq21uqzb.fsf@alter.siamese.dyndns.org>
On Mon, Sep 20, 2010 at 01:46, Junio C Hamano <gitster@pobox.com> wrote:
Show 10 quoted lines
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> Is there a reason for why this didn't get picked up other than falling
>> through the cracks?
>
> Simply because I wasn't actively collecting new topics during feature
> freeze, especially for small stuff that I knew that resending after
> release would be trivial and more efficient use of my time than queuing it
> in 'pu' and having to look at it every time I do another push-out in order
> to decide when to merge it to 'next'.

Rigth, I have no problem doing $whatever to get patches in, but the problem I often have is that I don't know what state things are in, and what I'm supposed to do at any given time.

E.g. in this case I submitted the "send-email: use catfile() to concatenate files" patch 2 days after this one, that one got into the next "What's cooking in git.git" post.

Since both were trivial fixes and there was no comment on this one I was inclined to think that it just fell through.

Should I generally re-send patches that I've sent, haven't had comments, and haven't appeared in subsequent "What's cooking in git.git" posts (given that some reasonable amount of time has passed since the original send) ?

Then there's stuff like my "git-am: Ignore whitespace before patches" which had some comments, but which *I* still think is OK as-is. Should I just keep pushing stuff like that until someone tells me to stop?

Thanks, from a list member somewhat confused about the patch queue :)
Previous: Junio C Hamano
Message 4 of 4 in “Makefile: add CC to TRACK_CFLAGS”
  1. Makefile: add CC to TRACK_CFLAGSÆvar Arnfjörð Bjarmason, Sep 12, 2010
  2. Ævar Arnfjörð BjarmasonSep 19, 2010
  3. Junio C HamanoSep 20, 2010
  4. Ævar Arnfjörð BjarmasonSep 20, 2010

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.