We need a doc to guide new contributors patch submission [was: Re: Working on -e trace]

[Dmitry V. Levin]

On Thu, May 12, 2016 at 07:46:01PM +0530, haris iqbal wrote:
> On Sat, May 7, 2016 at 1:07 AM, haris iqbal <haris.phnx at gmail.com> wrote:
> > On Fri, May 6, 2016 at 8:35 PM, Fabien Siron <fabien.siron at epita.fr> wrote:
> >> Quoting haris iqbal (2016-05-05 06:24:03)
> >>> On Sun, May 1, 2016 at 1:43 AM, Fabien Siron <fabien.siron at epita.fr> wrote:
> >>> > Hi,
> >>> >
> >>> > Quoting haris iqbal (2016-04-30 19:01:23)
> >>> >> Hi,
> >>> >>
> >>> >> So, this is my attempt at writing the wiki. Comments and suggestions are
> >>> >> welcome.
> >>> >
> >>> > It should be maybe interesting to add the --reroll-count=X to format-patch
> >>> > as it is very convenient to do patch versions.
> >>>
> >>> Yes. That looks useful. But, it seems a little detailed for a "Basic
> >>> guide" like this one.
> >>
> >> It just replaces the subject field, both lines do the same thing:
> >> $ git format-patch -1 <commit> --author="<Your Name>" \
> >>   --subject-prefix="[PATCH v<version number>]"
> >> $ git format-patch -1 <commit> --author="<Your Name>" \
> >>   --reroll-count=<version number>
> >>
> >> It seems easier for me.
> >
> > Cool, I can change that.
> >
> >> By the way, if you want to do a patch of the last commit, <commit> can be
> >> empty. For example:
> >> $ git format-patch -1 --reroll-count=<version number>
> >
> > I put that because
> >
> > $ git format-patch -1 <commit>
> >
> > can be used for any single commit, be it the last or the nth.
> 
> Hey, Just a reminder. Anything to be changed in this? Or this is all set?

As this is a wiki markup, it seems natural to create a page at
https://sourceforge.net/p/strace/wiki/.  Could you do it?


-- 
ldv
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20160513/5d253341/attachment.bin>