public inbox for [email protected]
 help / color / mirror / Atom feed
From: Alviro Iskandar Setiawan <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Jens Axboe <[email protected]>,
	Pavel Begunkov <[email protected]>,
	 io-uring <[email protected]>,
	gwml <[email protected]>,
	 Alviro Iskandar Setiawan <[email protected]>
Subject: Re: [PATCH liburing v2 2/4] src/Makefile: Add header files as dependency
Date: Thu, 10 Mar 2022 17:56:27 +0700	[thread overview]
Message-ID: <CAOG64qNJUTwsn1aLuMzNh3m8tVEStkJV2tL=BzU4Kt89-f25vw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>

On Thu, Mar 10, 2022 at 5:50 PM Ammar Faizi wrote:
> You should add the dependency files to .gitignore, otherwise we will have
> these files untracked after build.
>
>    Untracked files:
>      (use "git add <file>..." to include in what will be committed)
>            src/queue.ol.d
>            src/queue.os.d
>            src/register.ol.d
>            src/register.os.d
>            src/setup.ol.d
>            src/setup.os.d
>            src/syscall.ol.d
>            src/syscall.os.d
>
> Also, when doing `make clean`, the dependency files should be removed.

lmao, i forgot, oc, i'll be sending v3

-- Viro

  reply	other threads:[~2022-03-10 10:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 10:32 [PATCH liburing v2 0/4] Changes for Makefile Alviro Iskandar Setiawan
2022-03-10 10:32 ` [PATCH liburing v2 1/4] src/Makefile: Remove `-fomit-frame-pointer` from default build Alviro Iskandar Setiawan
2022-03-10 10:32 ` [PATCH liburing v2 2/4] src/Makefile: Add header files as dependency Alviro Iskandar Setiawan
2022-03-10 10:50   ` Ammar Faizi
2022-03-10 10:56     ` Alviro Iskandar Setiawan [this message]
2022-03-10 10:32 ` [PATCH liburing v2 3/4] test/Makefile: Add liburing.a as a dependency Alviro Iskandar Setiawan
2022-03-10 10:32 ` [PATCH liburing v2 4/4] examples/Makefile: " Alviro Iskandar Setiawan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOG64qNJUTwsn1aLuMzNh3m8tVEStkJV2tL=BzU4Kt89-f25vw@mail.gmail.com' \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox