From: Larsen <larsen007@web.de>
To: development@lists.ipfire.org
Subject: Re: Bug #10918 was: [ANNOUNCE] Good First Bugs
Date: Mon, 19 Oct 2015 22:01:10 +0200 [thread overview]
Message-ID: <op.x6rq78htcahio0@honk.fritz.box> (raw)
In-Reply-To: <DUB406-EAS3422FCE33A5F4D4F67731149C3A0@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
> Thanks again for guidelines,just one question more, what command/GUI
> output you use to make correct patch diff output on Windows?
== Create a patch ==
* Activate your local feature branch
* Rebase, when the remote branch has been updated inbetween:
* Right-click on the folder where the IPFire-code is located
* TortoiseGit > Rebase...
* Branch: Your local feature branch
* Upstream: next
* Select the newest ID and start the rebase
* Right-click on the folder where the IPFire-code is located
* TortoiseGit > Revision graph
* Select the block "next - origin/next"
* While holding the ctrl-key select your local feature branch
* Right-click > Unified diff
* Ctrl+Shift+S to save the patch to a file
Not 100% sure about the rebase procedure, but has been working till then =)
hth,
Lars
next parent reply other threads:[~2015-10-19 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DUB406-EAS3422FCE33A5F4D4F67731149C3A0@phx.gbl>
2015-10-19 20:01 ` Larsen [this message]
[not found] <DUB117-W12478B47C395BD80636DA359C3A0@phx.gbl>
2015-10-19 12:05 ` Larsen
2015-10-19 18:36 ` Larsen
[not found] <DUB117-W82174113D55546D54C78F49C3A0@phx.gbl>
2015-10-19 10:34 ` Larsen
[not found] <DUB117-W1390532CAFBEB3ACC60D1E69C3C0@phx.gbl>
2015-10-17 11:51 ` 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.x6rq78htcahio0@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