sox-devel@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: "Jaromír Mikeš" <mira.mikes@gmail.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: "Måns Rullgård" <mans@mansr.com>, sox-devel@lists.sourceforge.net
Subject: Re: man pages - fix
Date: Sun, 19 Nov 2017 09:14:03 +0100	[thread overview]
Message-ID: <CAG_ZyaCvR+Eww6C=KS+BUgqJ0ck+oMg6+G7UR3_rusQPCLjr1A@mail.gmail.com> (raw)
In-Reply-To: <20171118231210.GA24342@starla>


[-- Attachment #1.1: Type: text/plain, Size: 1172 bytes --]

2017-11-19 0:12 GMT+01:00 Eric Wong <normalperson@yhbt.net>:

> Jaromír Mikeš <mira.mikes@gmail.com> wrote:
> > Hi,
> >
> > we found little problem in sox man pages please consider use attached
> patch.
> > The warning said "table wider than line width"
>
> Sure, no objections to the actual patch, here.
>
>
> I'm curious how you generate the patch, since the headers seem
> machine-generated, but it's clearly not from "git format-patch"
>

​I got  patch from gabor.karsay@gmx.at as attachment ( without a header )
I added a header dep-3 header (manually)

http://dep.debian.net/deps/dep3/

maybe if I would use this result would be better?
$quilt header --dep3 -e


>
> Personally, I don't mind patch attachments at all (though some
> people do and prefer inline patches)
>
> However, "git format-patch" allows us to use "git am" to apply the
> patch while preserve authorship and commit message information,
> making life easier for folks applying the patches :)
>

​I will investigate git format-patch ​to understand how to make thing
easier for upstream.
Nevertheless DEP-3 is debian patch header

best regards

mira

[-- Attachment #1.2: Type: text/html, Size: 2409 bytes --]

[-- Attachment #2: Type: text/plain, Size: 202 bytes --]

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

[-- Attachment #3: Type: text/plain, Size: 158 bytes --]

_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel

      reply	other threads:[~2017-11-19  8:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-18 22:31 man pages - fix Jaromír Mikeš
2017-11-18 23:12 ` Eric Wong
2017-11-19  8:14   ` Jaromír Mikeš [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-list from there: mbox

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

  List information: https://lists.sourceforge.net/lists/listinfo/sox-devel

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

  git send-email \
    --in-reply-to='CAG_ZyaCvR+Eww6C=KS+BUgqJ0ck+oMg6+G7UR3_rusQPCLjr1A@mail.gmail.com' \
    --to=sox-devel@lists.sourceforge.net \
    --cc=mans@mansr.com \
    --cc=normalperson@yhbt.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/sox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).