From: Vinicius Monego <monego@posteo.net>
To: Sharlatan Hellseher <sharlatanus@gmail.com>, 51765@debbugs.gnu.org
Subject: [bug#51765]
Date: Tue, 04 Jan 2022 23:01:15 +0000 [thread overview]
Message-ID: <c3991c3a9db8f8fb2d904baccd7e0f2c181ae82b.camel@posteo.net> (raw)
In-Reply-To: <CAO+9K5p1RGRZb=m5xpDBg7A1_R43T=wkavxbb_h=7DMKdM+CiA@mail.gmail.com>
Em ter, 2022-01-04 às 21:39 +0000, Sharlatan Hellseher escreveu:
> Hi!
>
> Thank you for fead back @Vinicius Monego !
>
> I've added aditional changes to all mentioned patches but I've not
> created patch list from scratch. Let me know if would be easy to
> merge
> patches first.
>
The best way is to rebase to and amend the commits in the series and
send it from scratch again formatted with v2, v3, etc using --reroll-
count=2 in git format-patch.
You can also submit the patches using `git send-email --
to="NNN@debbugs.gnu.org" <patches>` where NNN is the ID of the issue,
here 51765. Check [1] to see how to configure it.
If you can merge them somehow it is preferable.
[1] https://git-send-email.io/
next prev parent reply other threads:[~2022-01-04 23:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 13:17 [bug#51765] [PATCH]: gnu: Add python-gwcs Sharlatan Hellseher
2021-12-26 19:01 ` [bug#51765] Sharlatan Hellseher
2021-12-26 19:55 ` [bug#51765] [PATCH]: gnu: Add python-gwcs Mathieu Othacehe
2021-12-26 20:47 ` Sharlatan Hellseher
2021-12-26 20:55 ` Mathieu Othacehe
2022-01-02 22:48 ` Sharlatan Hellseher
2022-01-02 22:48 ` [bug#51765] Sharlatan Hellseher
2022-01-02 22:48 ` [bug#51765] Sharlatan Hellseher
2022-01-04 2:41 ` [bug#51765] Vinicius Monego
2022-01-04 21:39 ` [bug#51765] Sharlatan Hellseher
2022-01-04 23:01 ` Vinicius Monego [this message]
2022-01-14 23:40 ` [bug#51765] Sharlatan Hellseher
2022-01-02 22:48 ` [bug#51765] Sharlatan Hellseher
2022-01-02 22:49 ` [bug#51765] Sharlatan Hellseher
2022-01-02 22:49 ` [bug#51765] Sharlatan Hellseher
2022-01-02 22:49 ` [bug#51765] Sharlatan Hellseher
2022-01-04 21:39 ` [bug#51765] Sharlatan Hellseher
2022-01-04 21:40 ` [bug#51765] Sharlatan Hellseher
2022-01-04 21:40 ` [bug#51765] Sharlatan Hellseher
2022-01-04 21:40 ` [bug#51765] Sharlatan Hellseher
2022-01-04 21:40 ` [bug#51765] Sharlatan Hellseher
2022-01-14 23:40 ` [bug#51765] [PATCH 1/6] gnu: python-asdf: Update to 2.8.3 Sharlatan Hellseher
2022-01-14 23:40 ` [bug#51765] [PATCH 2/6] gnu: Add asdf-transform-schemas Sharlatan Hellseher
2022-01-14 23:40 ` [bug#51765] [PATCH 3/6] gnu: Add asdf-coordinates-schemas Sharlatan Hellseher
2022-01-14 23:40 ` [bug#51765] [PATCH 4/6] gnu: Add asdf-astropy Sharlatan Hellseher
2022-01-14 23:40 ` [bug#51765] [PATCH 5/6] gnu: Add asdf-wcs-schemas Sharlatan Hellseher
2022-01-14 23:40 ` [bug#51765] [PATCH 6/6] gnu: Add gwcs Sharlatan Hellseher
2022-01-30 15:07 ` bug#51765: [PATCH 1/6] gnu: python-asdf: Update to 2.8.3 Vinicius Monego
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=c3991c3a9db8f8fb2d904baccd7e0f2c181ae82b.camel@posteo.net \
--to=monego@posteo.net \
--cc=51765@debbugs.gnu.org \
--cc=sharlatanus@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.