From: Larsen <larsen007@web.de>
To: development@lists.ipfire.org
Subject: Re: Sending in patches
Date: Mon, 11 Jan 2016 21:40:20 +0100 [thread overview]
Message-ID: <op.ya3c1iobcahio0@honk.fritz.box> (raw)
In-Reply-To: <1452462866.5665.3.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
On Sun, 10 Jan 2016 22:54:26 +0100, Michael Tremer
<michael.tremer(a)ipfire.org> wrote:
> I find this process with "git send-email" very easy and I am
> not sure where the problems could be.
I am using TortoiseGit with Windows 7. I don't know if this tool supports
"git send-email" and I wouldn't want to use command line git (it is
annoying to use more than one tool for the same job, IMHO). Therefore, I
create a patch file using TortoiseGit (I need a workflow reminder for this
to get it right), then send the contents with Thunderbird where I have to
remember to disable line wrap (also using a workflow reminder text).
In other projects (using Github), IMHO it is much easier to push to one's
own repository and create a merge request to the upstream repository.
Discussion can take place with that merge request.
In case you are open to using other tools in place of Patchwork, what
about Gitlab?
Lars
next prev parent reply other threads:[~2016-01-11 20:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 21:54 Michael Tremer
2016-01-11 20:40 ` Larsen [this message]
2016-01-15 1:25 ` Michael Tremer
2016-01-15 8:07 ` IT Superhack
2016-01-15 19:24 ` R. W. Rodolico
2016-01-16 14:45 ` Michael Tremer
2016-01-16 16:07 ` Matthias Fischer
2016-01-16 14:48 ` Michael Tremer
2016-01-16 18:07 ` Larsen
2016-01-17 19:17 ` Michael Tremer
2016-01-28 17:36 ` Larsen
2016-01-29 2:13 ` Michael Tremer
2016-01-12 18:08 ` Matthias Fischer
2016-01-15 1:28 ` Michael Tremer
[not found] <DUB406-EAS128B6703A1A0778E8A258779CC90@phx.gbl>
2016-01-12 23:51 ` Michael Tremer
2016-01-13 4:39 ` Xaver4all
2016-01-15 1:29 ` Michael Tremer
[not found] <DUB406-EAS163F3237DC6DE1AF244CD409CCE0@phx.gbl>
2016-01-16 14:53 ` Michael Tremer
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=op.ya3c1iobcahio0@honk.fritz.box \
--to=larsen007@web.de \
--cc=development@lists.ipfire.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
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