Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v7 4/4] doc/examples/transcode_aac: Bump date
Date: Mon, 2 May 2022 15:18:41 +0530
Message-ID: <f938339f-fdcf-3bf5-633a-d90c5b5aa9bd@gyani.pro> (raw)
In-Reply-To: <CAKp+PPrQEAh8WG=202mADwWLbv876kDVPPPqkR8fwD+_hYBF+w@mail.gmail.com>



On 2022-05-02 03:13 pm, Andreas Unterweger wrote:
> On Mon, 2 May 2022 at 11:38, Gyan Doshi <ffmpeg@gyani.pro> wrote:
>> Removed whitespace errors in first two patches and pushed the set as
>>
>> e13429c9c4...40f2ea971f
> Thank you. Any hints on how I can avoid these types of errors in the future?

You had stray tabs on newlines. So I suspect your editor auto-indents on 
new lines. Shut that off. And the ffmpeg source code files only work 
with spaces, not tabs, so if your editor allows it, set it to insert 4 
spaces when Tab key is pressed.

Regards,
Gyan

>
> Best,
> Andreas
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

      reply	other threads:[~2022-05-02  9:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02  7:31 Andreas Unterweger
2022-05-02  8:19 ` Andreas Unterweger
2022-05-02  8:39   ` Gyan Doshi
2022-05-02  8:53     ` Andreas Unterweger
2022-05-02  9:37       ` Gyan Doshi
2022-05-02  9:43         ` Andreas Unterweger
2022-05-02  9:48           ` Gyan Doshi [this message]

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=f938339f-fdcf-3bf5-633a-d90c5b5aa9bd@gyani.pro \
    --to=ffmpeg@gyani.pro \
    --cc=ffmpeg-devel@ffmpeg.org \
    /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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git